From gtm-skills
Identifies networking targets via persona matrix and drafts researched value-add cold emails (≤200 words), LinkedIn requests (≤300 chars), and hiring follow-ups (120–160 words) for job search, pivots, or partnerships.
npx claudepluginhub manojbajaj95/claude-gtm-plugin --plugin gtm-skillsThis skill uses the workspace's default tool permissions.
Relationship-first outreach built on research and value. The goal is to start a conversation by giving something, not asking for something.
Drafts personalized outreach messages for LinkedIn connections, hiring managers, or recruiters using hook + proof + proposal structure. Limits to under 300 characters for connection requests.
Researches prospects via web or connected enrichment/CRM, then drafts personalized cold emails, subjects, and LinkedIn messages.
Activate for: outreach, write email, LinkedIn message, cold email, cold outreach, personalised email, personalise, draft message, first touch, intro email, introduction email, ghostwrite, write for me, email draft, DM, direct message, InMail, connection request, WhatsApp message, outreach message, sales message, prospecting email. NOT for: multi-touch sequences (use sequence), post-call follow-ups (use follow-up), marketing content creation (use content-creation), ad copy or subject lines (use copywriting).
Share bugs, ideas, or general feedback.
Relationship-first outreach built on research and value. The goal is to start a conversation by giving something, not asking for something.
Mode 1 — Identify targets:
Mode 2 — Draft outreach for a specific person (cold networking):
Mode 3 — Hiring manager follow-up:
Before generating targets, establish:
| Question | Why It Matters |
|---|---|
| What's your goal? | Job, partnership, learning, visibility |
| What's your current context? | Title, company, background |
| What industry/function? | Narrows the search |
| Do you have any warm connections? | Starting point for introductions |
| What's your timeline? | Urgency affects strategy |
| Dimension | Options |
|---|---|
| Seniority | Peer / +1 level / +2 levels (max) |
| Accessibility | Active on LinkedIn, writes publicly, open profiles |
| Relevance | Working on what you want to learn/join/partner with |
| Warmth | Shared community, school, company, mutual connection |
Rank targets by:
For each target:
Use browser tools to read the full profile (expand all sections):
| Tool | MCP Name | Use For |
|---|---|---|
| Screenshot | mcp__computer-use__screenshot | Full page capture |
| Navigate | mcp__Claude_in_Chrome__navigate | Go to LinkedIn URL |
| Get page text | mcp__Claude_in_Chrome__get_page_text | Extract full profile text |
| Playwright fallback | mcp__plugin_compound-engineering_pw__browser_snapshot | Accessibility tree |
Extraction steps:
Search for additional context beyond LinkedIn:
[Name] [Company] interview OR podcast OR talk[Company] goals challenges [current year][Name] article OR newsletter OR writing[Company] funding hiring newsCapture:
Generate 5–10 ideas. Every angle must answer: "What's in it for them?"
| # | Angle | Example |
|---|---|---|
| 1 | Share a resource they'd genuinely care about | Article on a problem they mentioned |
| 2 | React to something they published — specific insight | "Your take on X made me think of Y" |
| 3 | Extend or challenge their public work | "I tried your framework, here's what I found" |
| 4 | Offer a skill/perspective they don't have | Fresh context from a different industry |
| 5 | Introduce them to someone useful | Connector play |
| 6 | Flag an opportunity they might not know about | Event, grant, community, tool |
| 7 | Share a relevant win related to their challenge | "We solved X, happy to share what worked" |
| 8 | Give feedback on something they're building | Beta test, review, honest take |
| 9 | Ask a specific expert question that's flattering to their depth | Shows you've done the homework |
| 10 | Surface a shared interest or community | Common ground, not flattery |
Structure:
Subject: [2–4 words, lowercase, looks internal — not a pitch]
[Specific hook — one observation about them, their work, or their company]
[One sentence connecting it to why you're reaching out]
[Your value offer — what you're giving, not asking for]
[Soft CTA — "Worth a look?" / "Thought you'd find this useful" / "Happy to share more if helpful"]
[Name]
Rules:
Structure:
[Specific observation about their work] + [one-line reason to connect] + [optional: soft opener]
Examples:
Rules:
Use when you've applied for a role and want to reach out personally to the hiring manager. This is not a cold pitch — it's a human note that shows you did the homework and know why you specifically fit.
Subject: [role name] — a specific note
[One concrete reference to something they've written, built, or said publicly —
connect it directly to the problem you'd solve in the role]
[One paragraph: who you are + your most relevant proof point + a link]
[Optional: honest acknowledgment of any prior attempt at this company —
honesty + persistence reads well]
[Soft CTA — 15 minutes / calendar link]
[Name]
Admit the obvious about yourself — state the thing that's been true all along that makes you the right fit, as if you're finally saying it out loud. Don't hide behind credentials. Open with identity, not job title.
Example opening pattern:
"Your piece on [X] is exactly the problem I've been working on from [the other side / a different angle]."
Then: who you are in one line → one proof point with a link → honest context → soft ask.
Before drafting any format, verify you have:
| Mistake | Why It Fails | Fix |
|---|---|---|
| Generic opener | Ignored immediately | Specific observation about their work |
| Asking for coffee chat | Too much friction, too early | Share something useful first |
| Multiple asks | Confusing | Pick one: share, reply, or simple yes/no |
| Long cold email | Won't be read | Under 200 words, ideally under 100 |
| Flattery without substance | Feels like a template | Cite the specific thing you liked |
| No value offer | It's a take, not a give | Always lead with what they get |
| Mentioning referral in first message | Kills rapport before it starts | Build relationship first |
| Credentials dump to hiring manager | Reads like a cover letter | Lead with their work, then one proof point |