本文へ移動
cccskills
無料GitHub で公開

linkedin-dm-outreach

This skill should be used when the user asks to "write a LinkedIn message", "draft a connection request", "help me reach out to someone on LinkedIn", "write an InMail", "message this person", or when the prospect-researcher skill identifies a high-value contact worth reaching out to. Also triggered by "how should I approach [person/company]" in a LinkedIn context.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md5.6 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

LinkedIn DM Outreach

Purpose

Write personalized LinkedIn messages — connection requests, InMails, and follow-up messages — that get responses instead of being ignored. Every message must demonstrate genuine relevance: why THIS person, why NOW, why the user is worth responding to.

Voice Loading

Load the user's voice via voice-master's overlay resolution before drafting:

  1. Read ../voice-master/SKILL.md and follow its User Calibration Overlay section to load exemplars and voice-dimensions from the out-of-repo overlay (or template fallback with warning if no overlay).
  2. This skill's medium is professional. Select professional-medium exemplars from whatever voice-master loads.
  3. Read ../voice-master/references/anti-slop.md — apply the Universal and Professional / LinkedIn sections.

If no overlay is present, voice-master falls back to generic voice guidance and warns — note this in your output.

DMs are the most personal LinkedIn format — sounding templated here is fatal. One bad outreach message can permanently close a door.

Message Types

Connection Request (300 characters max)

The hardest format. 300 characters to establish relevance and earn a click.

Rules:

  • Name a specific reason for connecting (shared interest, their content, mutual connection, specific role/company)
  • No generic "I'd love to add you to my network"
  • No pitching in the connection request — ever
  • If there's no genuine reason to connect, don't send the request

Structure: "[Specific reference to them or their work]. [Why connecting makes sense for both sides — in one sentence]."

First Message (after connecting)

Sent after a connection request is accepted, or to an existing connection.

Rules:

  • Thank them for connecting (brief, not gushing)
  • Reference something specific about them or their work
  • State your reason for reaching out clearly
  • Ask one specific question or make one specific offer
  • Keep under 150 words — respect their time
  • No "I hope this message finds you well"
  • No walls of text about yourself

Structure:

  • Line 1: Brief genuine acknowledgment
  • Line 2-3: Why you're reaching out (specific, relevant)
  • Line 4: One clear ask or offer

Follow-Up Message

If the first message got no response after 5-7 days.

Rules:

  • Maximum ONE follow-up. Two unanswered messages = they're not interested.
  • Add new value — don't just "bump" or "circle back"
  • Shorter than the first message
  • No guilt ("I know you're busy but...")
  • Accept that silence is an answer

Warm Introduction Request

Asking a mutual connection to introduce you to someone.

Rules:

  • Make it easy for the introducer — provide a brief, forwardable blurb
  • Explain why the introduction makes sense for all three parties
  • Never pressure — "only if you think it makes sense"

Research Integration

Before drafting any outreach, gather intelligence on the recipient:

  • Their recent posts and content (what they care about)
  • Their current role and company (what they're dealing with)
  • Mutual connections (potential introduction path)
  • Shared interests or background (common ground)
  • Their company's recent news (relevant context)

If the prospect-researcher skill has already run on this target, use its findings. If not, perform lightweight research before writing.

Outreach Scenarios

Job Search

Goal: Get a conversation about opportunities. Approach: Lead with what you can do for them, not what you want. Reference specific challenges their company/team faces. Ask about the team or the work, not about open positions directly.

Client Acquisition

Goal: Start a relationship that could lead to business. Approach: Never pitch in the first message. Offer genuine value first (insight, introduction, resource). Build rapport before discussing services. The goal is a conversation, not a sale.

Networking

Goal: Build a genuine professional relationship. Approach: Reference specific shared interests or complementary expertise. Suggest a concrete (low-commitment) next step — a specific article exchange, a brief call, a shared event.

Recruiting / Hiring

Goal: Attract a candidate. Approach: Lead with why you noticed THEM specifically (not "we have an exciting opportunity"). Be transparent about the role and company. Respect that they may not be looking.

Output Format

recipient: <name and context>
message_type: <connection_request | first_message | follow_up | intro_request>
scenario: <job_search | client_acquisition | networking | recruiting>
research_used: |
  <key findings about the recipient that informed the message>
message: |
  <the message text>
character_count: <for connection requests — must be under 300>
rationale: |
  <why this approach and angle>

References

  • ../voice-master/SKILL.md — Voice authority; follow its User Calibration Overlay section to load professional exemplars from the user overlay
  • ../voice-master/references/anti-slop.md — Universal + Professional/LinkedIn anti-slop rules
  • ../prospect-researcher/SKILL.md — Deep research on outreach targets

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Forward Deployed Engineer delivery contract for AWS engagements, build-first artifacts, grounded cost estimates, Well-Architected review, evolution roadmap

日本語の概要は準備中です。原文の説明を表示しています。

WingedGuardian/GENesis-AGI962026年10月13日 更新

Canonical guide to Genesis browser automation - layers (Camoufox, Chromium, the user's Chrome over CDP, TinyFish, desktop), per-tool timeouts, safety gates, verify-after-act, what a click checks (scroll, hit test, covered targets), overlays, iframes, tabs, and failure diagnosis

日本語の概要は準備中です。原文の説明を表示しています。

WingedGuardian/GENesis-AGI962026年10月13日 更新

cc-update

無料

Update Claude Code (the CC CLI / "clog code") to a new version, or bump the pinned CC version. Use when the user asks to update Claude Code, bump the CC pin, evaluate a new CC release, or says "clog code update". Routes to the canonical, standardized process in docs/reference/cc-compatibility.md — do NOT re-derive the update mechanism by grepping every time. Do NOT use for general "what changed in CC" trivia with no intent to update.

日本語の概要は準備中です。原文の説明を表示しています。

WingedGuardian/GENesis-AGI962026年10月13日 更新

This skill should be used when a session's job is to DRIVE OPEN PRs TO MERGE rather than to write new code — "close out the open PRs", "review and fix the open PRs", "what's blocking our PRs", "which PRs are mergeable". It owns the In Review column: it reads each PR's gate status, verifies and fixes review findings on PRs OTHER sessions built, replies in-thread, and stops at the merge gate for the user's per-PR approval. Do NOT load it for building a feature and opening its PR — that is a build session (`genesis-development`).

日本語の概要は準備中です。原文の説明を表示しています。

WingedGuardian/GENesis-AGI962026年10月13日 更新

Code understanding tool selection. Use when exploring architecture, finding definitions, tracing call chains, assessing blast radius of changes, or debugging code paths in the Genesis codebase.

日本語の概要は準備中です。原文の説明を表示しています。

WingedGuardian/GENesis-AGI962026年10月13日 更新

End-to-end content creation and publishing. Takes a topic (or generates one), drafts in the user's voice, gets approval via Telegram, and publishes to Medium via browser automation. Invoke with "publish a post about X", "write and publish to Medium", "content-publish", or when an ego-dispatched session needs to create and distribute content.

日本語の概要は準備中です。原文の説明を表示しています。

WingedGuardian/GENesis-AGI962026年10月13日 更新

WingedGuardian のスキルをすべて見る

このスキルの問題を報告する