Cold email
A Claude Code plugin that adds an agentic skills framework, with MCP's and a meta prompting processes. Inspired by "Superpowers" & "Figma Console MCP", but not just for development or design; but for all aspect within the digital production cycle.
npx -y skills add bromso/metapowers --skill cold-emailAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Create outbound email strategy and templates
SKILL.md
2.1 KB, 531 tokens by cl100k_base, as published. Nobody here has run it
Cold Email
Design cold outbound email campaigns for "$ARGUMENTS". Create personalized email templates, follow-up sequences, and targeting criteria.
Prerequisites
Read .metapowers/marketing/$ARGUMENTS/00-strategy.md. If this file does not exist, tell the user:
Phase 0 (Strategy) has not been completed for "$ARGUMENTS". Run
/marketing:customer-research $ARGUMENTSfirst, or use--skip-checksto bypass.
If --skip-checks is present in $ARGUMENTS, skip this check and log to .metapowers/marketing/$ARGUMENTS/skip-log.md.
Process
-
Read context:
- Read
.metapowers/marketing/$ARGUMENTS/00-strategy.mdfor audience and value proposition - Read
plugins/marketing/shared/campaign-plan-template.mdfor structure
- Read
-
Define targeting criteria:
- Ideal customer profile (ICP) for outbound
- Company firmographics: size, industry, tech stack, growth signals
- Contact persona: title, department, seniority
- Intent signals: hiring, funding, tech changes, content engagement
-
Design email sequence:
- 3-5 email sequence with timing (typically days 1, 3, 7, 14)
- Each email: different angle or value prop
- Personalization strategy: what's personalized per recipient?
- Follow-up logic: when to stop, when to escalate
-
Write email templates:
- For each email: subject line (2-3 variants), body, CTA
- Keep emails short (under 150 words)
- Lead with relevance, not pitch
- Include specific personalization placeholders
- Compliance: include opt-out, identify sender, no deceptive subjects
-
Write the artifact — append to
.metapowers/marketing/$ARGUMENTS/03-convert.mdunder a## Cold Emailsection:- ICP & Targeting — who to target and why
- Sequence Design — timing and logic
- Email Templates — full copy for each email
- Personalization Guide — what to customize per recipient
- Compliance Notes — CAN-SPAM, GDPR requirements
Output
Cold email strategy written to .metapowers/marketing/$ARGUMENTS/03-convert.md. Present the full email sequence for review.
Gives 0 of the 12 instructions most sales crm skills give in 531 tokens
Counted across 361 of the 361 authors here whose files we hold, read 2026-08-06
- Read product marketing context before writing if it existsin 22 of 361, across 14 files
- keep the ask low-frictionin 16 of 361, across 7 files
- Call RUBE_SEARCH_TOOLS firstin 15 of 361, across 5 files
- personalize every outbound messagein 13 of 361, across 4 files
- confirm connection status is activein 13 of 361, across 4 files
- Keep forwardable blurbs under 100 wordsin 13 of 361, across 4 files
- State if personalization context is missingin 13 of 361, across 4 files
- Cut any sentence that does not drive a replyin 13 of 361, across 4 files
- Use proof instead of adjectivesin 12 of 361, across 3 files
- Use a single, low-friction call to actionin 12 of 361, across 4 files
- Calibrate tone to the specific audiencein 12 of 361, across 3 files
- Make each follow-up email add new valuein 12 of 361, across 6 files
Said here and by no other author read
- Read strategy and campaign plan templates
- Define ideal customer profile and personas
- Identify firmographic and intent targeting signals
- Vary angle or value proposition per email
- Lead with relevance not pitch
- Include personalization placeholders
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.