← ClaudeAtlas

cold-email-pipelinelisted

Run a cold email campaign end to end on RouterGrowth from one targeting sentence: Research, List, Grade, Verify, Write, Send. Reads a directives folder (ICP, lead source filters, negative keywords, qualification rubric, copy rules) so "target independent mortgage brokers in Lyon" becomes a graded, verified, personalised campaign sent from an inbox the workspace owns, with two human gates. Use when the user wants to launch cold outreach, build and qualify a lead list, write cold email at scale, or run the prospecting pipeline. The daily loop after the first send is the sdr-daily skill.
RouterGrowth/skills · ★ 2 · AI & Automation · score 75
Install: claude install-skill RouterGrowth/skills
# Cold email pipeline Six stages over a directives folder the user configures once. The stages that touch data call RouterGrowth capabilities; the stages that judge (grading, writing) run on you. Two gates: the final list and copy, and the first live send. Everything between them runs on its own. ``` Research → List → Grade → Verify → Write → Send brief raw keep clean per- inbox the leads ICP list lead workspace only copy owns ``` Raw lead lists are 30 to 50% wrong-ICP. Grade and Verify exist so the campaign does not email agencies, dead sites and wrong-geo firms, tank the reply rate and burn the domain. ## Before you start - Load the core `routergrowth` skill (https://www.routergrowth.com/SKILL.md) if it is not loaded. Confirm access with the free `balance` tool or `routergrowth balance`. - Check `directives/` exists in the working project. If not, copy the `directives/` folder next to this file into the project and ask the user to fill `icp.md`, `lead-source.md` and `email-copy.md`. Those three are mandatory; the others have sensible defaults. When no human is in the loop (a scheduled or delegated run), fill them from the brief you were given, say so in the files, and treat the caller's budget as the approval at both gates. - Run the free `email.inboxes`. The campaign sends from an inbox the workspace owns on a verified domain. If there is none, stop and run the cold email infrastructure setup first