distributions/claude/skills/networking-outreach/SKILL.md
Build professional relationships through strategic outreach—cold emails, LinkedIn engagement, informational interviews, and follow-up sequences. Authentic connection over transactional networking. Triggers on networking, cold outreach, LinkedIn strategy, or informational interview requests.
npx skillsauth add organvm-iv-taxis/a-i--skills networking-outreachInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Build genuine professional relationships at scale.
| Transactional | Relational | |---------------|------------| | "What can you do for me?" | "How can I be useful?" | | One-time ask | Ongoing relationship | | Immediate need | Long-term investment | | Extract value | Create value |
Before asking for anything:
| Category | Who | Why | |----------|-----|-----| | Direct targets | Hiring managers, recruiters | Decision makers | | Warm connections | Alumni, former colleagues | Shared context | | Industry peers | Similar role, different company | Mutual learning | | Thought leaders | Content creators, speakers | Visibility + learning | | Connectors | Well-networked individuals | Access to network |
For each person:
Attention: Hook that earns the read
Interest: Why you're reaching out
Desire: What's in it for them / credibility
Action: Clear, easy ask
Subject: [Specific, relevant, not clickbait]
Hi [Name],
[One sentence showing you did research—specific to them]
[Why you're reaching out—be direct]
[Brief credibility—why you, why now]
[Specific, low-commitment ask]
[Graceful out—acknowledge they're busy]
Best,
[Your name]
[One-line signature]
Subject: Quick question about [their specialty] at [Company]
Hi Sarah,
I came across your post about migrating to microservices at Stripe—
the part about managing tech debt during the transition resonated
with challenges I'm facing.
I'm a senior engineer exploring platform roles, and Stripe's
infrastructure work is particularly interesting to me.
Would you have 20 minutes for a call? I'd love to hear how you
approached [specific thing]. Happy to work around your schedule.
No worries if you're swamped—I know these requests add up.
Best,
[Name]
| Pattern | Example | |---------|---------| | Mutual connection | "Alex Chen suggested I reach out" | | Specific reference | "Your talk on X at Y" | | Direct ask | "Quick question about [topic]" | | Shared context | "Fellow [school] alum in [field]" | | Value offer | "Resource on [topic you discussed]" |
❌ Generic templates with no personalization ❌ Long emails (>150 words for cold) ❌ Asking for a job directly ❌ No clear ask ❌ Attachments on first email ❌ Following up aggressively
Hi [Name],
[One sentence of context—how you found them, what you have in common]
[Why you want to connect—specific, genuine]
[Name]
Example:
Hi Marcus,
I saw your comment on Lenny's post about PLG metrics—your point
about activation vs. engagement really clarified something I've
been wrestling with.
Would love to connect and follow your thinking on product growth.
[Name]
Daily (5-10 min):
Weekly (30 min):
Quality Comments:
Keep it specific and low-commitment:
Career Path:
Role Insight:
Industry/Company:
Advice:
Closing:
Day 0: Initial email
Day 4-5: Bump email
Day 10-14: Final follow-up with new angle
Bump Email:
Subject: Re: [original subject]
Hi [Name],
Just floating this back up in case it got buried.
[One new sentence of value or context]
[Name]
Final Follow-Up:
Subject: Re: [original subject]
Hi [Name],
I'll assume now isn't a good time. No worries at all.
If things change, I'd still love to connect about [topic].
Best,
[Name]
Day 0: Thank you email
Week 2-4: Share relevant article/resource
Month 1-2: Update on your progress
Ongoing: Engage with their content
Day 0: Apply
Day 3-5: Reach out to hiring manager/recruiter
Day 10: Follow up if no response
Post-interview: Same day thank you
| Name | Company | How Found | Status | Last Contact | Next Action | Notes | |------|---------|-----------|--------|--------------|-------------|-------| | [Name] | [Co] | [Source] | [Stage] | [Date] | [Action] | [Notes] |
references/email-templates.md - Full template libraryreferences/linkedin-scripts.md - Connection and message templatesreferences/tracking-template.md - CRM spreadsheetdevelopment
Dry-run audit + targeted cleanup for shell command history. Currently wraps atuin (stats today, prune, dedup with dated preview artifacts); extensible to zsh/bash/mcfly backends. Always previews before applying — apply commands are echoed for the human to run, never auto-executed. Triggers on "/shell-history-hygiene", "audit atuin", "audit shell history", "clean shell history", "atuin prune", "atuin dedup", "shell history hygiene", "history cleanup". Replaces ad-hoc one-liners (e.g. `... | tee cmd > file.txt` which wrote two files, swallowed dedup output, and left a junk `cmd` file).
tools
Guided Cowork setup — install role-matched plugins, connect your tools, try a skill.
development
Manage AI agent session lifecycles with structured phases (FRAME, SHAPE, BUILD, PROVE), context preservation across sessions, handoff protocols, and session metadata tracking. Triggers on session management, agent lifecycle, or multi-session workflow requests.
tools
Parse a session transcript into a structured Session Governance Index — an annotated bibliography of every file modified and commit made, internal-energy accounting (tool uses, estimated tokens), shipped-vs-tasked atom tally, and classification of missing items as Gaps or Vacuums. Triggers on "visibility-schema-substrate-sweep", "session cascade audit", "session governance audit", or any request to summarize what a session actually produced versus what it was asked to produce.