outreach
Skill1 starsChanged 4 months agoMITView on GitHub
Generate the right outreach message for any contact or company. Argument: [person name / company / context — e.g., 'alumni at Google' or 'recruiter at Stripe']
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 and triage.
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
Google CloudSkilltriage
Gather context on a change or bug and plan the implementation.
Also in 3 projects that use this
Other versions18 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 18
- QuixiAI/agi-memory★ 623same name
- QuixiAI/Hexis★ 623same name
- andrew-shwetzer/career-ops-plugin★ 501same name
- andrew-shwetzer/career-ops-plugin-do-not-fork-currently-updating-v2-★ 500same 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
8 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.
In this repository11 other files it gives its agents.
- applySkill
- evaluateSkill
- followupSkill
- generic-letterSkill
- humanizerSkill
- interviewSkill
- patternsSkill
- resume-customizerSkill
- salary-negotiateSkill
- track-applicationSkill
- update-memorySkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 3 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 18 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Read ${CLAUDE_PLUGIN_ROOT}/skills/resume-customizer/references/career-tools.md for the 6 outreach templates and personalization guidance.
- Distinctive: line 25
If the context is ambiguous, ask which situation applies before generating.
- Very specific: line 29
Before writing anything, read the Contact and Last follow-up columns for this company in ${CLAUDE_PLUGIN_ROOT}/references/applications.md, …
- Distinctive: line 48
Never use generic placeholders in the final output — fill them in or explicitly mark what the user needs to fill in manually before sending.
- Very specific: line 52
Run the humanizer skill in this plugin on the drafted message before you output it.
- Distinctive: line 62
Follow-up timing: [when to follow up if no response]
“Common” is measured: kept by at least 6 in 10 of the 18 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
You are generating outreach messages for the user's job search. The user has described the target contact or company.
STEP 1: Read the outreach templates
Read ${CLAUDE_PLUGIN_ROOT}/skills/resume-customizer/references/career-tools.md for the 6 outreach templates and personalization guidance. Read ${CLAUDE_PLUGIN_ROOT}/references/YOUR_PROFILE.md for the user's name, title, phone, LinkedIn, portfolio, and key achievements.
STEP 2: Identify the right template
Select based on the user's input:
| Situation | Template |
| Cold LinkedIn connection request | Template 1 (300 char limit) |
| LinkedIn InMail to hiring manager | Template 2 |
| Cold email to recruiter | Template 3 |
| WhatsApp / direct message to warm contact for referral | Template 4 |
| Following up after no response | Template 5 |
| Thank you after interview | Template 6 |
If the context is ambiguous, ask which situation applies before generating.
STEP 3: Check what was already sent
Before writing anything, read the Contact and Last follow-up columns for this company in
${CLAUDE_PLUGIN_ROOT}/references/applications.md, the tracker the track-application skill keeps.
A follow-up that repeats a message already sent costs the relationship. If the row shows a recent
touch, say so and confirm with the user before generating. If the tracker does not exist yet, or has
no row for this company, say that there is no record of earlier contact and continue. Never treat
the rows in applications.example.md as real history.
STEP 4: Personalize the message
Mandatory personalizations:
- Replace
[NAME]with the person's name if provided - Replace
[COMPANY]with the actual company name - Replace
[SPECIFIC]with something real about their work or company news if mentioned - Replace
[ROLE]with the actual role if known - For Template 2 (InMail): include a specific company challenge or product reference
- For Template 4 (warm DM): use first name only, keep casual tone
- Pull the user's name, title, scope, achievements, phone, and LinkedIn from
YOUR_PROFILE.md
Never use generic placeholders in the final output — fill them in or explicitly mark what the user needs to fill in manually before sending.
STEP 5: Voice pass
Run the humanizer skill in this plugin on the drafted message before you output it. An outreach
draft that still reads as AI-written is not finished.
STEP 6: Output the message
Output the ready-to-send message clearly formatted, followed by:
- Channel: [where to send this]
- Length: [character / word count]
- What to customize before sending: [any remaining gaps]
- Follow-up timing: [when to follow up if no response]
For warm outreach, include phone from YOUR_PROFILE.md. For email / InMail, include LinkedIn from YOUR_PROFILE.md.
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.