outboundlisted

# Outbound - Outbound Sales Execution A skill that sequentially reaches out to prospects on the sales list via email, contact forms, and SNS DMs. For each prospect, sends a message via an available channel and records the result in the DB. After all processing, generates a summary report. ## Steps ### 1. Setup - Project ID: `$0` (required) - Approach count: `$1` (default: 30) **Compliance pre-flight (run before anything else).** Call `mcp__plugin_lead-ace_api__get_compliance_status`. If `ready: false`, **abort immediately** — do not load documents, do not call `get_outbound_targets`. Report to the user which fields are missing (from the `missing` array) and direct them to the URL in `fix_url` (e.g. `https://app.leadace.ai/workspace-settings`). Tell them to re-run this skill once the workspace fields are saved. Sending without these will fail with HTTP 412 at the send call regardless, so bailing here saves the token cost of draft generation. Load documents via MCP: Call `mcp__plugin_lead-ace_api__get_document` with `projectId: "$0"` and `slug: "business"`. Call `mcp__plugin_lead-ace_api__get_document` with `projectId: "$0"` and `slug: "sales_strategy"`. Call `mcp__plugin_lead-ace_api__get_document` with `projectId: "$0"` and `slug: "env_status"`. Source of truth for connected tools (Gmail SaaS / Claude in Chrome), saved by `/setup` or `/lead-ace`. Hold the result as `ENV` (or `null` if the document doesn't exist). The send-mode capability gate below decides whether to