coldemail

star 0

Writes high-converting cold emails using proven copywriting frameworks (PAS, AIDA, BAB). Generates subject lines, email body, and optional follow-ups from structured inputs. Invoke with /coldemail followed by a JSON blob containing icp, offer, pain_points, proof, and cta fields.

glazerm2019-rgb By glazerm2019-rgb schedule Updated 1/29/2026

name: coldemail description: Writes high-converting cold emails using proven copywriting frameworks (PAS, AIDA, BAB). Generates subject lines, email body, and optional follow-ups from structured inputs. Invoke with /coldemail followed by a JSON blob containing icp, offer, pain_points, proof, and cta fields. argument-hint: {"icp":"","offer":"","pain_points":[],"proof":"","cta":""} disable-model-invocation: true

Cold Email Skill

Generate cold emails that get opened, read, and replied to. Uses data-backed copywriting frameworks and best practices from analysis of millions of cold emails.

Key Metrics to Beat

  • Average open rate: 39%
  • Average reply rate: 8.5%
  • Target with this skill: 20%+ reply rate

Input Handling

  1. Parse $ARGUMENTS as JSON
  2. If JSON parse fails, ask for missing required fields (max 3 prompts)

Required Fields

Field Description
offer Product/service being pitched
icp Ideal customer profile (who receives this)
pain_points 1-3 specific problems you solve
proof One metric, case study, or credible signal
cta Desired action (low-friction ask)

Optional Fields

Field Default Description
company_name - Target company
persona - Job title (VP Sales, Head of Ops)
tone casual, direct Writing style
framework PAS Copywriting framework: PAS, AIDA, or BAB
personalization - Trigger event, recent news, or specific insight
constraints - banned_words array, required_tokens array
substitutions - Word replacement map
include_followup false Include follow-up sequence
sequence_length 1 Number of follow-ups (1-3)

Copywriting Frameworks

Select framework based on situation. See references/frameworks.md for detailed guidance.

PAS (Problem → Agitate → Solve) — Default

Best for: Direct response, urgent problems, clear solutions

  1. Problem: Name specific pain point prospect faces
  2. Agitate: Amplify consequences of inaction
  3. Solve: Present your solution as the antidote

AIDA (Attention → Interest → Desire → Action)

Best for: Building relationship, multiple value points, nurturing

  1. Attention: Hook with personalization or insight
  2. Interest: Address their challenge
  3. Desire: Show transformation/results
  4. Action: Clear, low-friction CTA

BAB (Before → After → Bridge)

Best for: Transformation stories, case studies, aspirational outcomes

  1. Before: Current painful state
  2. After: Desired future state
  3. Bridge: Your solution connects them

Output Format

SUBJECT OPTIONS:
1. [2-4 words, question or benefit]
2. [personalized variant]
3. [curiosity hook]

EMAIL:
[60-120 words, plain text, framework structure]

FOLLOW-UP 1 (if requested):
[Context-based, not reminder-based, new angle or value]

FOLLOW-UP 2 (if requested):
[Different hook, social proof, or breakup angle]

Subject Line Rules

Data shows 2-4 word subject lines get 46% open rates. Questions outperform all other types.

Do:

  • Use questions ("Quick question about [X]?")
  • Personalize with name/company when possible
  • Create curiosity without clickbait
  • Front-load value

Don't:

  • Use urgency words (ASAP, urgent, now)
  • Generic greetings ("Hello, friend")
  • Marketing jargon
  • Exceed 50 characters
  • Use ALL CAPS (despite marginal data advantage, feels spammy)

Email Body Rules

Length: 60-120 words optimal. Never exceed 150.

Structure:

  1. Line 1: Personalized hook OR direct pain point (no "I hope this finds you well")
  2. Line 2-3: Context + proof (tie to their situation)
  3. Line 4: Value proposition (what they get)
  4. Line 5: Single, low-friction CTA

The BYAF Principle: Acknowledge their freedom to say no. "If not, no worries" doubles positive response rates.

Quality Checklist

Before outputting, verify:

  • Under 120 words
  • No banned words (see rules/banned_words.txt)
  • Claims tied to provided proof only
  • One CTA, not multiple
  • Written FOR them, not AT them (prospect is focus)
  • Personalization is specific, not generic
  • No links unless explicitly provided
  • Plain text, no HTML formatting

Follow-up Strategy

Follow-ups should add value, not just remind. See references/followup_strategy.md.

Spacing: 3-5 days apart Tone: Progressively shorter, still valuable Final email: "Breakup" style with door left open

References

  • references/frameworks.md — Detailed framework examples
  • references/followup_strategy.md — Multi-touch sequence guidance
  • references/psychology.md — Persuasion principles
  • templates/ — Structure templates
  • rules/banned_words.txt — Words that kill conversions
  • rules/style_rules.md — Tone and formatting
  • examples/ — Input/output examples by framework
Install via CLI
npx skills add https://github.com/glazerm2019-rgb/cold-email-skill --skill coldemail
Repository Details
star Stars 0
call_split Forks 0
navigation Branch main
article Path SKILL.md
More from Creator
glazerm2019-rgb
glazerm2019-rgb Explore all skills →