UNPKG

@sellable/install

Version:

One-command installer for Sellable MCP in Claude Code, Codex, and Hermes

79 lines (68 loc) • 3.45 kB
--- name: find-leads description: Find or source prospects, build and watch a live Sellable lead list, and export the finished list without creating a campaign. visibility: public allowed-tools: - mcp__sellable__get_auth_status - mcp__sellable__start_cli_login - mcp__sellable__wait_for_cli_login - mcp__sellable__get_active_workspace - mcp__sellable__list_workspaces - mcp__sellable__set_active_workspace - mcp__sellable__get_subskill_prompt - mcp__sellable__get_subskill_asset - mcp__sellable__search_subskill_prompts - mcp__sellable__get_provider_prompt - mcp__sellable__bootstrap_find_leads - mcp__sellable__get_find_leads_run - mcp__sellable__update_find_leads_run - mcp__sellable__wait_for_find_leads_run - mcp__sellable__cancel_find_leads - mcp__sellable__reissue_find_leads_watch_link - mcp__sellable__preflight_find_leads_provider - mcp__sellable__lookup_sales_nav_filter - mcp__sellable__search_sales_nav - mcp__sellable__search_prospeo - mcp__sellable__search_signals - mcp__sellable__select_promising_posts - mcp__sellable__import_leads - mcp__sellable__wait_for_lead_list_ready - mcp__sellable__get_rows_minimal - mcp__sellable__export_table_csv --- # Sellable Find Leads Use this public command when the user asks to find or source prospects, build a lead list, watch the list fill in real time, review leads, or export the list. It works without an existing campaign. ## Writing to the customer Everything you write to the customer (Slack messages, questions, progress notes, summaries, the campaign brief) follows ASD-STE100 Simplified Technical English at about 80%: - One idea per sentence. One instruction per sentence. - An instruction has at most 20 words; any other sentence at most 25. - Active voice: say who does the action ("I added 60 people"). - Simple tenses only: present, simple past, and "will". - Common words with one meaning. Use the same word for the same thing every time. - No idioms, slang or phrasal verbs where one verb works: "start", not "kick off". - An instruction starts with its verb: "Reply to Priya.", "Connect your LinkedIn." - Keep small words such as "the", "a" and "to". Use a list for more than two items. Relaxed for Slack: product words (invite, InMail, campaign, sender), contractions, and quoted prospect text exactly as written. This rule is for text to the customer only. Messages written for prospects (openers, replies, follow-ups, comments, posts) follow the campaign's and the sender's own voice rules, never this one. ## Load the canonical workflow 1. Call `mcp__sellable__get_auth_status({})` and complete login/workspace setup if required. 2. Load `mcp__sellable__get_subskill_prompt({ subskillName: "find-leads-v2" })`. Continue chunks until `hasMore` is false. 3. Load `mcp__sellable__get_subskill_asset({ subskillName: "find-leads-v2", assetPath: "core/flow.v1.json" })`. 4. Execute that prompt and flow as the operational source of truth. Do not emulate the workflow from memory or local files. If prompt or asset loading fails, use `search_subskill_prompts({ query: "find-leads-v2", includePublic: true, includeInternal: true })`, retry once, then give the workflow's reinstall/reload guidance. Keep approval questions in the current chat. A source-plan approval allows only the bounded provider search. A later import approval is required before rows are materialized. Export uses the source list directly.