networking-outreach
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.
Best use case
networking-outreach is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using networking-outreach should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/networking-outreach/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How networking-outreach Compares
| Feature / Agent | networking-outreach | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# Networking Outreach Build genuine professional relationships at scale. ## Networking Philosophy ### The Mindset Shift | 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 | ### The Give-First Principle Before asking for anything: - Share relevant content - Make introductions - Offer help or expertise - Engage with their work --- ## Outreach Strategy ### Target Identification | 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 | ### Research Before Outreach For each person: - Current role and company - Career path - Shared connections - Recent content/achievements - Potential common ground --- ## Cold Email Framework ### The AIDA Structure ``` Attention: Hook that earns the read Interest: Why you're reaching out Desire: What's in it for them / credibility Action: Clear, easy ask ``` ### Cold Email Template ``` 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] ``` ### Example: Informational Interview Request ``` 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] ``` ### Subject Line Patterns | 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]" | ### What NOT to Do ❌ 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 --- ## LinkedIn Strategy ### Profile Optimization - **Headline**: Not just title—value proposition - **About**: First person, story-driven, keywords - **Experience**: Accomplishments, not duties - **Featured**: Best work, portfolio links - **Activity**: Regular engagement ### Connection Requests ``` 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] ``` ### Engagement Strategy **Daily** (5-10 min): - Comment thoughtfully on 2-3 posts - React to content from targets **Weekly** (30 min): - Post original content or insight - Send 3-5 connection requests - Message 2-3 existing connections **Quality Comments**: - Add insight, not just agreement - Ask thoughtful questions - Share relevant experience - Tag when genuinely relevant --- ## Informational Interviews ### The Ask Keep it specific and low-commitment: - 15-20 minutes (not 30) - Phone/video (their preference) - Flexible on timing - Clear topic ### Preparation - Research their background thoroughly - Prepare 5-7 questions - Know what you want to learn - Have your own story ready ### Question Framework **Career Path**: - "How did you get into [field]?" - "What led you from [A] to [B]?" **Role Insight**: - "What does a typical week look like?" - "What surprised you about this role?" **Industry/Company**: - "What trends are you watching?" - "What's the culture really like?" **Advice**: - "What would you do differently?" - "What should I be learning?" **Closing**: - "Who else should I talk to?" - "How can I be helpful to you?" ### During the Call - Be on time (early) - Let them talk (80/20) - Take notes - Watch the time - Ask for referrals naturally - Offer value if you can ### After the Call - Thank you email within 24 hours - Connect on LinkedIn if not already - Follow up on anything discussed - Stay in touch (content shares, updates) --- ## Follow-Up Sequences ### After No Response (Cold) ``` 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] ``` ### After Informational Interview ``` Day 0: Thank you email Week 2-4: Share relevant article/resource Month 1-2: Update on your progress Ongoing: Engage with their content ``` ### After Job Application ``` 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 ``` --- ## Tracking System ### Simple Spreadsheet | Name | Company | How Found | Status | Last Contact | Next Action | Notes | |------|---------|-----------|--------|--------------|-------------|-------| | [Name] | [Co] | [Source] | [Stage] | [Date] | [Action] | [Notes] | ### Status Stages - Researching - Outreach sent - Replied - Scheduled - Completed - Follow-up due - Warm contact --- ## References - `references/email-templates.md` - Full template library - `references/linkedin-scripts.md` - Connection and message templates - `references/tracking-template.md` - CRM spreadsheet
Related Skills
taxonomy-modeling-design
Phase 2 of the pentaphase structural-overhaul protocol. Classifies entities, standardizes attributes, establishes relationships, and designs the access framework. Use when the user invokes phase 2 of an overhaul, asks to "design the taxonomy" or "model the structure", or has completed a landscape audit and is ready to redesign. Consumes phase-1-landscape-report.md; produces phase-2-taxonomy-model.md.
systemic-ingestion-normalization
Phase 4 of the pentaphase structural-overhaul protocol. Purges redundancies, enriches and aligns legacy entities to the new schema, executes phased ingestion into the new environment, and audits integrity. Use when the user invokes phase 4 of an overhaul, asks to "migrate the data" or "ingest into the new system", or has a configured environment ready to accept legacy entities. Consumes phase-3-environment-spec.md; produces phase-4-ingestion-report.md.
system-environment-configuration
Phase 3 of the pentaphase structural-overhaul protocol. Translates the taxonomy model into objective technical criteria, evaluates candidate mechanisms or frameworks, instantiates the chosen architecture, and programs validation rules. Use when the user invokes phase 3 of an overhaul, asks to "select a system" or "configure the environment", or has a taxonomy model and is ready to choose technology. Consumes phase-2-taxonomy-model.md; produces phase-3-environment-spec.md.
pentaphase-orchestrator
Threads the full five-phase structural-overhaul protocol — landscape discovery, taxonomy design, environment configuration, systemic ingestion, governance evolution — for any substrate the user names. Use when the user requests a structural overhaul, system redesign, or end-to-end restructuring of a documentation system, asset registry, code monorepo, knowledge base, or operational workflow; or when they explicitly invoke the pentaphase methodology. Coordinates handoffs between phase-skills and seats validation gates between phases.
landscape-discovery-audit
Phase 1 of the pentaphase structural-overhaul protocol. Inventories assets, maps current flow, identifies friction, and defines value metrics for any substrate. Use when the user invokes phase 1 of an overhaul, requests a baseline audit, asks to "discover the landscape" of a system, or wants to understand current state before redesigning. Produces phase-1-landscape-report.md.
governance-evolution-protocol
Phase 5 of the pentaphase structural-overhaul protocol. Codifies operational protocols, onboards the ecosystem of participants, programs behavior monitoring, and establishes an iteration cadence so the substrate evolves rather than calcifies. Use when the user invokes phase 5 of an overhaul, asks to "establish governance" or "lock in the protocols", or has completed ingestion and is ready to declare the substrate operational. Consumes phase-4-ingestion-report.md; produces phase-5-governance-charter.md, which closes the protocol.
dimension-surfacing
Surfaces the parallel domain dimensions implicit in a dense or minimal prompt. Use when a user prompt is small on the surface but plainly implies multiple independent domains needing different expertise; when explicitly invoked by the coliseum-orchestrator skill as Phase 1; or when the user asks "what dimensions does this prompt encode" or "what axes does this break into." Produces a named dimension set where each dimension is independently executable and not a paraphrase of another.
coliseum-dispatch
Dispatches a composed set of assignment envelopes to domain-expert subagents in parallel, in a single message with multiple Agent tool calls. Enforces the no-pingpong gate via the pingpong-detector agent before any dispatch fires. Use when invoked by the coliseum-orchestrator as Phase 3; when envelopes are already composed and the next step is parallel execution; or when the user asks to "fan out" or "dispatch in parallel." Produces a dispatch log capturing what was sent, when, and where returns land.
assignment-composition
Wraps each surfaced dimension as a self-contained 9-section autonomous-work-assignment envelope — scope, context, success criteria, allowed tools, return format, handoff — all the recipient subagent needs to execute without coming back. Use when invoked by coliseum-orchestrator as Phase 2; when dimensions are named and the next step is to make each independently dispatchable; or when the user asks "compose this as an assignment." The no-pingpong gate validates each envelope before dispatch.
workspace-autopsy-governance
Conducts a full automated autopsy of the current workspace directory to map files, identifies structural issues, proposes a restructuring plan (the signal), and establishes unified governance using templates. Use this skill when a user asks to map, restructure, reorganize, or apply new governance to an existing messy repository.
workshop-presentation-design
Design engaging workshops, conference talks, and educational presentations. Covers learning objectives, activity design, slide craft, and facilitation techniques. Triggers on workshop design, presentation prep, talk structure, or training session requests.
webhook-integration-patterns
Designs reliable webhook systems with proper delivery guarantees, retry logic, signature verification, and idempotent processing for event-driven integrations.