outreach
Skill501 starsChanged 7 months agoMITView on GitHub
Draft personalized outreach messages for LinkedIn connections, hiring managers, or recruiters. Creates targeted messages using a hook + proof + proposal structure. Under 300 characters for connection requests. Use when someone says 'draft outreach', 'message the recruiter', 'reach out to', or 'write a LinkedIn message'.
18 other projects use a version of this.
Adopted by
Most recently taken up by
- guaardvark/guaardvarktheir own version, first seen Nov 5, 2026
- cismontane-harris2642/signal-prospecting-kittheir own version, first seen Nov 1, 2026
- saksham10arora-dotcom/everything-claude-codextheir own version, first seen Nov 1, 2026
- ShawhinT/non-coding-skillstheir own version, first seen Oct 29, 2026
- jaredhhawk/claude-skillstheir own version, first seen Oct 25, 2026
- FakharEAli/book-skillstheir own version, first seen Oct 25, 2026
Used with
Projects with it also use profile.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
julienamorganSkillprofile
Researches the user's market, competitors, and competitive positioning to build a complete ICP profile. Shows findings for user approval before proceeding. Triggers: /profile, "research my market", "who are my competitors". Reads: ./gtm/company.md, ./gtm/icp.md. Writes: updates ./gtm/icp.md with competitive positioning. Standalone: yes (asks for domain if company.md missing).
Also in 3 projects that use this
Other versions18 projects use a version of this.
Word for word · 1
Edited · 0
None found.
Wrote their own version · 17
- QuixiAI/agi-memory★ 623same name
- QuixiAI/Hexis★ 623same name
- guaardvark/guaardvark★ 306same name
- saksham10arora-dotcom/everything-claude-codex★ 74same name
- ShawhinT/non-coding-skills★ 40same name
- emelia-io/claude-outreach★ 21same name
- alejopijuan/Claude-Code-Agency-Co-Founder★ 19same name
- Abhipaddy8/outreach-agent★ 17same name
- julienamorgan/signal-prospecting-kit★ 16same name
- FakharEAli/book-skills★ 3same name
7 more not listed
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.
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. 0 are common, 11 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 17 edited versions we read keep these.
11
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Create personalized outreach messages for job search networking.
- Very specific: line 20
Check data/research/{company}.md for company intelligence
- Very specific: line 21
Check data/evaluations/ for any evaluation at this company
- Distinctive: line 23
If no company research exists:
- Distinctive: line 32
If no specific contact named, suggest based on research file:
- Distinctive: line 46
Ask the user which type if not clear from context.
- Distinctive: line 104
NEVER draft messages that misrepresent the user's background
- Distinctive: line 105
NEVER suggest the user claim a connection that doesn't exist
- Distinctive: line 106
NEVER draft overly flattering or sycophantic messages
- Distinctive: line 107
Keep LinkedIn connection requests under 300 characters (hard limit)
- Distinctive: line 108
Every message must contain something specific (not a template)
- Distinctive: line 109
If no company research and no web search available, be honest: "This message would be stronger with specific company context.
- Distinctive: line 111
Consider researching them first."
“Common” is measured: kept by at least 6 in 10 of the 17 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Draft Outreach
Create personalized outreach messages for job search networking.
Step 0: Load Context
- Read
data/profile.yml - Check
data/research/{company}.mdfor company intelligence - Check
data/evaluations/for any evaluation at this company
If no company research exists:
"I don't have research on {company} yet. Better outreach comes from better intel. Want me to research them first, or should I draft something with what I know?"
Step 1: Identify the Contact
Parse user input for: contact name, title, company, platform.
If no specific contact named, suggest based on research file:
"Based on my research, here are contacts at {company}: {list from research} Who would you like to reach out to?"
Step 2: Determine Message Type
| Type | When | Length |
| LinkedIn connection request | No existing connection | Under 300 characters |
| LinkedIn message | Already connected | 100-200 words |
| Cold email | Have their email | 100-150 words |
| Follow-up | Already reached out, no response 5+ days | 50-75 words |
Ask the user which type if not clear from context.
Step 3: Generate Using 3-Part Structure
Part 1: Hook (about THEM, not you)
Reference something specific about the company, their work, or a recent event.
Bad: "I'm really interested in your company" (about you) Bad: "I'd love to connect" (generic) Good: "Your team's work on {specific project/launch} caught my attention" Good: "I noticed {company} just {recent event from research}"
Part 2: Proof (one quantifiable thing about you)
One sentence. One number. Directly relevant to their world.
Bad: "I have 10 years of experience in marketing" Good: "I grew organic traffic 3x at {Company} in 8 months" Good: "I managed a $2M portfolio with 98% client retention"
Pull the most relevant proof point from the user's profile that connects to the target company's needs.
Part 3: Proposal (low-pressure ask)
Bad: "Can you refer me?" (presumptuous) Bad: "I'd love to pick your brain" (vague, one-sided) Good: "Would you be open to a 15-minute chat about what {team} looks for?" Good: "I'd appreciate any advice on standing out for the {role} opening"
Step 4: Output
## Outreach: {Contact Name} at {Company}
**Platform:** {LinkedIn connection / LinkedIn message / Email / Follow-up}
**Context:** {role or department}
---
{the message, properly formatted}
---
**Character count:** {n} / {limit for platform}
**Tone:** {Professional / Warm / Direct}Step 5: Offer Variations
"Want me to:
- Adjust the tone? (more formal / more casual / more direct)
- Write for a different platform? (email instead of LinkedIn)
- Draft a follow-up for if they don't respond in a week?"
Rules
- NEVER draft messages that misrepresent the user's background
- NEVER suggest the user claim a connection that doesn't exist
- NEVER draft overly flattering or sycophantic messages
- Keep LinkedIn connection requests under 300 characters (hard limit)
- Every message must contain something specific (not a template)
- If no company research and no web search available, be honest: "This message would be stronger with specific company context. Consider researching them first."
Does 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.

