Agent skill
cold-pitch
Write a cold outreach email to land a client. Timed to a specific trigger (new funding, visible gap, recent hire, content inconsistency). Structure follows observation → problem → solution → proof → next step. Under 150 words. Use when user needs a "cold email", "outreach email", "cold pitch", or "prospecting message".
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/cold-pitch
SKILL.md
Load Context First
Before executing this skill, read the following files from the project folder if they exist:
- USER.md — who the user is, how they think, how they work
- BUSINESS.md — their business, products, positioning, brand voice, content strategy
- ICP.md — their ideal customer, their language, their fears, what makes them buy
- Voice or brand voice skill — look for any installed skill related to voice, tone, or brand voice and apply it automatically
- Any additional context provided by the user in this session
Use all context silently. Do not reference or summarize files unless asked.
Cold Pitch Writer
Purpose: Write cold outreach emails that feel personal, relevant, and worth responding to. The key: tie every pitch to a specific trigger or observation about the prospect's business.
Core Principle
He who frames the problem owns the solution. Don't pitch your services. Identify a visible gap, articulate the problem better than the prospect can, then position yourself as the obvious solution.
The best cold pitches:
- Reference something specific about the prospect's business
- Identify a problem they haven't solved yet
- Position the sender as a peer, not a vendor
- Keep it brutally short (under 150 words)
Trigger Types
Every cold pitch should be timed to a specific trigger:
| Trigger | Why It Works | Example |
|---|---|---|
| New funding | They have budget and growth pressure | "Congrats on the Series A..." |
| New hire | Indicates growth area | "Saw you hired a Head of Content..." |
| Content gap | Visible problem you can solve | "I noticed your blog hasn't been updated since..." |
| Inconsistency | Shows they need help | "Your LinkedIn is strong but your newsletter is dormant..." |
| Launch/announcement | Timely and relevant | "Saw you just launched X — have you thought about..." |
| Competitor activity | Creates urgency | "I noticed [competitor] just started publishing about..." |
Structure (Under 150 Words)
Subject: [Short, specific, not salesy]
[Line 1: Observation about their business — shows you did homework]
[Line 2-3: The problem you've identified — articulate it clearly]
[Line 4: Your specific solution — what you'd do, not just "I help with X"]
[Line 5: One proof point — a result, a client, or a credential]
[Line 6: Clear next step — specific and low-friction]
[Sign-off]
Required Input
- Prospect name and business
- The trigger (what prompted this outreach)
- The observation (what gap or opportunity you see)
- User's relevant experience or proof point
Output Format
# Cold Pitch: [Prospect Name / Company]
**Trigger:** [What prompted this outreach]
**Word count:** [X]/150
---
**Subject:** [Subject line]
[Full email body]
---
## Alternative Versions
### Version B (Different angle):
**Subject:** [Subject]
[Full email]
### Version C (Shorter):
**Subject:** [Subject]
[Full email]
---
## Follow-Up Email (Send 3-5 days later if no response)
**Subject:** Re: [Original subject]
[Short follow-up — 2-3 sentences max. Add one new value point.]
Rules
- Under 150 words — shorter is almost always better
- No fluff — every sentence must earn its spot
- Subject line — short, specific, not salesy (never "Quick question" or "Opportunity")
- No "I just wanted to..." or "I hope this finds you well"
- One CTA only — "Would a 15-min call this week make sense?"
- First name only — "Hi Sarah" not "Dear Ms. Johnson"
- No attachments — nothing that triggers spam filters
- No long intros about yourself — prove value, don't explain your resume
Quality Checklist
- Tied to a specific trigger (not generic)
- Under 150 words
- Shows genuine observation about their business
- Problem is articulated clearly
- Solution is specific (not "I help with content")
- One proof point included
- CTA is specific and low-friction
- Subject line is short and non-salesy
- 3 versions provided (different angles)
- Follow-up email included
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?