Stats
Actions
Tags
From saleshandy
ICP-driven prospecting via Saleshandy Lead Finder. Use whenever the user asks to find, search, discover, source, get, or list prospects, leads, contacts, or people matching a natural-language description — e.g. "find HR managers at fintech SaaS", "get me CTOs in 51-200 employee SaaS companies", "show me marketing directors at series B startups", "I need 20 sales leaders in EU". Also handles "get emails for [people description]" and "find phone numbers for [ICP]". Wraps natural-language Lead Finder search, async enrichment (with credit-cost gating), and optional gated enrollment into a Saleshandy sequence step.
How this skill is triggered — by the user, by Claude, or both
Slash command
/saleshandy:discover-and-enrollThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The user has asked to discover prospects matching an ICP and possibly enroll them into a sequence. Execute the workflow in `${CLAUDE_PLUGIN_ROOT}/commands/discover-and-enroll.md` — read it first, then run it end-to-end.
The user has asked to discover prospects matching an ICP and possibly enroll them into a sequence. Execute the workflow in ${CLAUDE_PLUGIN_ROOT}/commands/discover-and-enroll.md — read it first, then run it end-to-end.
Treat the user's natural-language message as the equivalent of $ARGUMENTS in that file. Apply every gate in the command verbatim:
sage_search call per user turn, 6 per conversation. No fan-out.list_sequences and list_sequence_steps and wait for explicit picks.throttled: true signal.payload.results returned, and surface payload.resultUrl for the user to refine in the Saleshandy web app.The user does not need to type a slash command — your job is to recognize the intent and run this workflow.
npx claudepluginhub saleshandy/saleshandy-plugin --plugin saleshandyCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.