draft-outreach
Skill0 starsChanged 7 months agoMITView on GitHub
Research a prospect then draft personalized outreach. Uses web research by default, supercharged with enrichment and CRM. Trigger with "draft outreach to [person/company]", "write cold email to [prospect]", "reach out to [name]".
11 other projects use a version of this.
Adopted by
Most recently taken up by
- seonwooj0810/careerlooptheir own version, first seen Oct 20, 2026
- spirosbax/insaighttheir own version, first seen Oct 13, 2026
- anthropics/knowledge-work-pluginstheir own version, first seen Oct 13, 2026
- edu6565/claude-skillsword for word, first seen Oct 11, 2026
- youdcode/open-companytheir own version, first seen Sep 21, 2026
- sree-data/job-search-agenttheir own version, first seen Sep 11, 2026
Other versions11 projects use a version of this.
Word for word · 2
- edu6565/claude-skills★ 0100% same
- KevinReactiv8/claude-skills★ 0100% same
Edited · 0
None found.
Wrote their own version · 9
- anthropics/knowledge-work-plugins★ 35ksame name
- microsoft/dataverse-business-skills★ 51same name
- spirosbax/insaight★ 32same name
- alebgl77/claude-inc★ 21same name
- xx254/linkedin_skills★ 16same name
- youdcode/open-company★ 2same name
- CatchIntent/skills★ 0same name
- seonwooj0810/careerloop★ 0same name
- sree-data/job-search-agent★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository91 other files it gives its agents.
- ab-testSkill
- adsSkill
- analyzeSkill
- brand-contextSkill
- brand-memorySkill
- brand-storySkill
- briefSkill
- campaignSkill
- communitySkill
- competeSkill
- contentSkill
- docxSkill
- pdfSkill
- pptxSkill
- scheduleSkill
- setup-coworkSkill
- skill-creatorSkill
- xlsxSkill
- cowork-plugin-customizerSkill
- create-cowork-pluginSkill
- croSkill
- emailSkill
- funnelSkill
- gtm-engineSkill
- gtmSkill
- hookSkill
- landingSkill
- brand-voiceSkill
- campaign-planningSkill
- competitive-analysisSkill
- content-creationSkill
- performance-analyticsSkill
- ab-test-setupSkill
- ad-creativeSkill
- ai-seoSkill
- analytics-trackingSkill
- churn-preventionSkill
- cold-emailSkill
- competitor-alternativesSkill
- content-strategySkill
- copy-editingSkill
- copywritingSkill
- email-sequenceSkill
- form-croSkill
- free-tool-strategySkill
- launch-strategySkill
- marketing-ideasSkill
- marketing-psychologySkill
- onboarding-croSkill
- page-croSkill
- paid-adsSkill
- paywall-upgrade-croSkill
- popup-croSkill
- pricing-strategySkill
- product-marketing-contextSkill
- programmatic-seoSkill
- referral-programSkill
- revopsSkill
- sales-enablementSkill
- schema-markupSkill
- The first 60 shown.
The file
Files
Draft Outreach
Research first, then draft. This skill never sends generic outreach - it always researches the prospect first to personalize the message. Works standalone with web search, supercharged when you connect your tools.
Connectors (Optional)
| Connector | What It Adds |
| Enrichment | Verified email, phone, background details |
| CRM | Prior relationship context, existing contacts |
| Create draft directly in your inbox |
No connectors? Web research works great. I'll output the email text for you to copy.
How It Works
+------------------------------------------------------------------+
| DRAFT OUTREACH |
| |
| Step 1: RESEARCH (always happens first) |
| - Web search (default) |
| - + Enrichment (if enrichment tools connected) |
| - + CRM (if CRM connected) |
| |
| Step 2: DRAFT (based on research) |
| - Personalized opening (from research) |
| - Relevant hook (their priorities) |
| - Clear CTA |
| |
| Step 3: DELIVER (based on connectors) |
| - Email draft (if email connected) |
| - Copy for LinkedIn (always) |
| - Output to user (always) |
+------------------------------------------------------------------+Output Format
# Outreach Draft: [Person] @ [Company]
**Generated:** [Date] | **Research Sources:** [Web, Enrichment, CRM]
---
## Research Summary
**Target:** [Name], [Title] at [Company]
**Hook:** [Why reaching out now - the personalized angle]
**Goal:** [What you want from this outreach]
---
## Email Draft
**To:** [email if known, or "find email" note]
**Subject:** [Personalized subject line]
---
[Email body]
---
**Subject Line Alternatives:**
1. [Option 2]
2. [Option 3]
---
## LinkedIn Message (if no email)
**Connection Request (< 300 chars):**
[Short, no-pitch connection request]
**Follow-up Message (after connected):**
[Value-first message]
---
## Why This Approach
| Element | Based On |
|---------|----------|
| Opening | [Research finding that makes it personal] |
| Hook | [Their priority/pain point] |
| Proof | [Relevant customer story] |
| CTA | [Low-friction ask] |
---
## Email Draft Status
[Draft created - check ~~email]
[Email not connected - copy email above]
[No email found - use LinkedIn approach]
---
## Follow-up Sequence (Optional)
**Day 3 - Follow-up 1:**
[Short, new angle]
**Day 7 - Follow-up 2:**
[Different value prop]
**Day 14 - Break-up:**
[Final attempt]Execution Flow
Step 1: Parse Request
Input patterns:
- "draft outreach to John Smith at Acme" → Person + company
- "write cold email to Acme's CTO" → Role + company
- "reach out to sarah@acme.com" → Email provided
- "LinkedIn message to [LinkedIn URL]" → Profile providedStep 2: Research First (Always)
Use research-prospect skill internally:
1. Web search for company + person
2. If Enrichment connected: Get verified contact info, background
3. If CRM connected: Check for prior relationshipMust find before drafting:
- Who they are (title, background)
- What the company does
- Recent news or trigger
- Personalization hook
Step 3: Identify Hook
Priority order for hooks:
1. Trigger event (funding, hiring, news) → Most timely
2. Mutual connection → Social proof
3. Their content (post, article, talk) → Shows you did research
4. Company initiative → Relevant to their priorities
5. Role-based pain point → Least personal but still relevantStep 4: Draft Message
Email Structure (AIDA):
SUBJECT: [Personalized, <50 chars, no spam words]
[Opening: Personal hook - shows you researched them]
[Interest: Their problem/opportunity in 1-2 sentences]
[Desire: Brief proof point - similar company result]
[Action: Clear, low-friction CTA]
[Signature]LinkedIn Connection Request (<300 chars):
Hi [Name], [Mutual connection/shared interest/genuine compliment].
Would love to connect. [No pitch]LinkedIn Follow-up Message:
Thanks for connecting! [Value-first: insight, article, observation]
[Soft transition to why you reached out]
[Question, not pitch]Step 5: Create Email Draft
If email connector available:
1. Create draft with to, subject, body
2. Return draft link
3. Note: "Draft created - review and send"
If not available:
1. Output email text
2. Note: "Copy to your email client"Capability by Connector
| Capability | Web Only | + Enrichment | + CRM | |
| Personalized opening | Basic | Deep | With history | Same |
| Verified email | No | Yes | Yes | Yes |
| Background details | Public only | Full | Full | Full |
| Prior relationship | No | No | Yes | Yes |
| Auto-create draft | No | No | No | Yes |
Message Templates by Scenario
Cold Outreach (No Prior Relationship)
Subject: [Their initiative] + [your angle]
Hi [Name],
[Personal hook based on research - news, content, mutual connection].
[1 sentence on their likely challenge based on role/company].
[Brief proof: "We helped [Similar Company] achieve [Result]".]
Worth a 15-min call to see if relevant?
[Signature]Warm Outreach (Have Met / Mutual Connection)
Subject: Following up from [context]
Hi [Name],
[Reference to how you know them / who connected you].
[Why reaching out now - their trigger].
[Specific value you can offer].
[CTA]Re-Engagement (Went Dark)
Subject: [Short, curiosity-driven]
Hi [Name],
[Acknowledge time passed without being guilt-trippy].
[New reason to reconnect - their news or your news].
[Simple question to re-open dialogue].
[Signature]Post-Event Follow-up
Subject: Great meeting you at [Event]
Hi [Name],
[Specific memory from conversation].
[Value-add: article, intro, resource related to what you discussed].
[Soft CTA for next conversation].Email Style Guidelines
- Be concise but informative — Get to the point quickly. Busy people skim.
- No markdown formatting — Never use asterisks, bold (text), or other markdown. Write plain text that looks natural in any email client.
- Short paragraphs — 2-3 sentences max per paragraph. White space is your friend.
- Simple lists — If listing items, use plain dashes. No fancy formatting.
Good:
Here's what I can share:
- Case study from a similar company
- 15-min intro call this week
- Quick demo if helpfulBad:
**What I Can Offer:**
- **Case study** from a similar company
- **Intro call** this weekWhat NOT to Do
Generic openers:
- "I hope this email finds you well"
- "I'm reaching out because..."
- "I wanted to introduce myself"
Feature dumps:
- Long paragraphs about your product
- Multiple value props at once
- No clear CTA
Fake personalization:
- "I noticed you work at [Company]" (obviously)
- "Congrats on your role" (without context)
Markdown in emails:
- Using bold or italic asterisks
- Headers or formatted lists that won't render
Instead:
- Lead with something specific you learned
- One clear value prop
- One clear ask
- Plain text formatting only
Channel Selection
IF verified email available:
→ Email preferred (higher response rate)
→ Also provide LinkedIn backup
IF no email:
→ LinkedIn connection request
→ Follow-up message template for after connection
IF warm intro possible:
→ Suggest mutual connection outreach firstCompany Configuration [CUSTOMIZE]
## Outreach Settings
- My name: [Your Name]
- My title: [Your Title]
- My company: [Company Name]
- Value prop: [One sentence - what you help with]
## Signature
[Your preferred email signature]
## Proof Points
- [Customer 1]: [Result]
- [Customer 2]: [Result]
- [Customer 3]: [Result]
## CTA Options
- Default: "Worth a 15-min call?"
- Softer: "Open to learning more?"
- Specific: "Can I send over a quick demo?"
## Tone
- [Professional / Casual / Direct]
- Industry-specific language: [Yes/No]Example
Input: "draft outreach to the Head of Engineering at Notion"
Research finds:
- Name: David Tibbitts
- Recent news: Notion launched AI features
- Hiring: 5 ML engineer roles open
- Background: Ex-Facebook, Stanford CS
Output:
# Outreach Draft: David Tibbitts @ Notion
## Research Summary
**Target:** David Tibbitts, Head of Engineering at Notion
**Hook:** They're scaling AI features and hiring ML talent
**Goal:** Intro call about AI infrastructure
---
## Email Draft
**To:** david@notion.so
**Subject:** Notion's AI scaling + a thought
---
Hi David,
Saw Notion's AI rollout is gaining serious traction - congrats.
With 5 ML roles open, seems like you're scaling fast.
Curious how you're thinking about inference infrastructure
as usage grows. We helped [Similar Company] cut their AI
serving costs 40% while improving latency.
Worth a 15-min call to see if relevant to your roadmap?
Best,
[Name]
---
**Subject Alternatives:**
1. Notion AI + scaling question
2. Quick thought on Notion's ML hiring
---
## Email Draft Status
Draft created - check ~~emailDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

