Generated banner for Compose Outreach
Generated logo for Compose Outreach

Compose Outreach

AnthropicOfficialCreated by Common RoomDistributed by Anthropic

  • Skill
  • Content generator
  • Business and productivity
  • Apache-2.0
  • No issues found

From the author

Generate personalized outreach messages using Common Room signals. Triggers on 'draft outreach to [person]', 'write an email to [name]', 'compose a message for [contact]', or any outreach drafting request.
— the description by Common Room

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

Compose-outreach is a specialized skill designed to create high-relevance, personalized outreach content. By leveraging data from Common Room signals—such as community engagement, product usage, and external intent—the agent crafts tailored messages across three distinct formats: email, call scripts, and LinkedIn messages. It prioritizes recency and specificity to ensure every outreach attempt is grounded in verifiable activity, while providing an annotation of the signals used to help the user understand the strategic angle.

What it does

  • Retrieves and analyzes target contact or company data from Common Room.
  • Identifies high-value personalization hooks based on recency and relevance.
  • Generates three distinct outreach formats: email, call script, and LinkedIn message.
  • Performs web searches for external hooks when internal signal data is sparse.
  • Provides a brief rationale for the chosen signals and suggested outreach strategy.
  • Enforces strict length and tone constraints to ensure professional and effective communication.

When to use it

  • When you need to draft personalized outreach for a specific prospect or company.
  • When you want to leverage community engagement or product usage signals for sales.
  • When you need to reach out to a prospect but lack a strong, recent hook.
  • When you require consistent, multi-channel messaging for a single target.

Advantages

  • Ensures outreach is grounded in real, verifiable signals rather than generic templates.
  • Provides a structured, multi-format approach for consistent messaging.
  • Includes a fallback mechanism to prevent sending low-quality, fabricated outreach.
  • Optimizes LinkedIn messages for platform constraints and conversational tone.

Usage examples

“draft outreach to Sarah Jenkins at Acme Corp”
The agent retrieves Sarah's recent activity from Common Room, identifies a relevant hook (e.g., a recent community post), and generates a tailored email, call script, and LinkedIn message.
“write an email to the VP of Engineering at TechFlow”
The agent researches TechFlow's recent funding or hiring activity, identifies the best contact, and drafts professional outreach grounded in those specific business events.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/anthropics/compose-outreach/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip compose-outreach.zip -d .agents/skills

Documentation by Common Room

Compose Outreach

Generate three personalized outreach formats — email, call script, and LinkedIn message — grounded in Common Room signals for a specific company or contact.

Outreach Process

Step 1: Look Up the Target

Use Common Room MCP tools to find and retrieve data for the target (company and/or specific contact). Pull:

  • Recent product activity and engagement signals

  • Community activity (posts, questions, reactions)

  • 3rd-party intent signals (job postings, news, funding)

  • Relationship history (prior contact, meetings, email opens)

If the user specified a person, run contact-level research. If only a company was given, identify the best contact to target based on title, engagement, and role.

Step 2: Web Search for External Hooks (If CR Signals Are Thin)

If CR returned strong signals (recent activity, engagement, product usage), those should drive personalization — skip web search. If CR signals are thin or the prospect has little CR activity, run a web search for external hooks:

What to search:

  • "[company name]" funding OR acquisition OR launch OR announcement — last 30 days

  • "[contact full name]" "[company name]" — look for recent articles, interviews, LinkedIn posts, or conference talks

Prioritize external hooks that are:

  • Very recent (< 2 weeks) — the prospect is likely still thinking about it

  • Publicly visible — they know you could have seen it

  • Change-signaling — growth, new role, new product, new market

If the user explicitly asks for web search or external hooks, run it regardless of CR signal richness.

Step 3: Spark Enrichment (If Available)

If Spark is available, run enrichment on the target contact to get persona classification, background, and influence signals. Use this to calibrate tone and message angle.

Step 4: Identify the Best Hooks

From the signal data, identify the 1–3 strongest personalization hooks. Rank by:

  1. Recency — happened in the last 7–14 days

  2. Specificity — a concrete action they took, not a general trend

  3. Relevance — connects directly to a value your product delivers

Good hooks: posted a question in the community about X, just hired 5 engineers, recently started using [feature], company just raised Series B, trial nearing expiration, champion just changed jobs.

Bad hooks: "I noticed you're a customer" or generic industry trends.

Step 5: Generate All Three Formats

Use the strongest hooks to write all three formats. Each format has different constraints and conventions — follow the format-specific guidelines in references/outreach-formats-guide.md.

Always produce all three, clearly labeled.

When the user's company context is available (see references/my-company-context.md), ground the value bridge and pitch in the user's specific product and positioning.

Step 6: Annotate Your Choices

After the three drafts, include a brief note (2–4 sentences) explaining:

  • Which signals were used and why they were chosen

  • Any assumptions made (e.g., inferred call objective)

  • Alternative angles if the primary hook doesn't land

Output Format

## Outreach for [Name / Company]

### 📧 Email

**Subject:** [Subject line]

[Email body — 3–5 sentences]

---

### 📞 Call Script

**Opening:**
[Opening line — conversational, 1–2 sentences]

**Value Bridge:**
[Why you're calling and why now — 2–3 sentences tied to a signal]

**Ask:**
[Single, low-friction ask — e.g., 15-minute call, specific question]

---

### 💼 LinkedIn Message

[Under 300 characters. Warm, personal, no pitch.]

---

### Signal Notes
[2–4 sentences: which signals were used, why, and any alternative angles]

When Signal Data Is Sparse

If Common Room returns minimal data on the target (e.g., just name, title, tags — no activity, no scores, no Spark):

  1. Do not draft outreach from thin air. Outreach grounded in fabricated signals is worse than no outreach.

  2. Run web search first — this becomes your primary personalization source. Look for recent news, LinkedIn posts, conference talks, company announcements.

  3. If web search also returns little, present what you have honestly and ask the user for context:

## Outreach for [Name / Company] — Limited Data

**What I found:**
[Only the real data from CR and web search]

**I don't have enough signal to draft personalized outreach yet.** To write something strong, I'd need:
- Recent activity or engagement signals
- Context you have from prior conversations
- A specific reason for reaching out now

Can you share any of the above?

Quality Standards

  • Every message must reference something specific — generic outreach is not acceptable output

  • Match tone to context: warm and conversational for inbound/community signals; more formal for cold/executive outreach

  • The LinkedIn message must be under 300 characters — no exceptions

  • The call script must be speakable naturally — read it aloud mentally to check rhythm

  • Never fabricate signals — only reference data retrieved from Common Room or web search

Reference Files

  • references/outreach-formats-guide.md — detailed format rules, examples, and tone guidelines for each channel

Files

SKILL.md

Compose Outreach

Generate three personalized outreach formats — email, call script, and LinkedIn message — grounded in Common Room signals for a specific company or contact.

Outreach Process

Step 1: Look Up the Target

Use Common Room MCP tools to find and retrieve data for the target (company and/or specific contact). Pull:

  • Recent product activity and engagement signals

  • Community activity (posts, questions, reactions)

  • 3rd-party intent signals (job postings, news, funding)

  • Relationship history (prior contact, meetings, email opens)

If the user specified a person, run contact-level research. If only a company was given, identify the best contact to target based on title, engagement, and role.

Step 2: Web Search for External Hooks (If CR Signals Are Thin)

If CR returned strong signals (recent activity, engagement, product usage), those should drive personalization — skip web search. If CR signals are thin or the prospect has little CR activity, run a web search for external hooks:

What to search:

  • "[company name]" funding OR acquisition OR launch OR announcement — last 30 days

  • "[contact full name]" "[company name]" — look for recent articles, interviews, LinkedIn posts, or conference talks

Prioritize external hooks that are:

  • Very recent (< 2 weeks) — the prospect is likely still thinking about it

  • Publicly visible — they know you could have seen it

  • Change-signaling — growth, new role, new product, new market

If the user explicitly asks for web search or external hooks, run it regardless of CR signal richness.

Step 3: Spark Enrichment (If Available)

If Spark is available, run enrichment on the target contact to get persona classification, background, and influence signals. Use this to calibrate tone and message angle.

Step 4: Identify the Best Hooks

From the signal data, identify the 1–3 strongest personalization hooks. Rank by:

  1. Recency — happened in the last 7–14 days

  2. Specificity — a concrete action they took, not a general trend

  3. Relevance — connects directly to a value your product delivers

Good hooks: posted a question in the community about X, just hired 5 engineers, recently started using [feature], company just raised Series B, trial nearing expiration, champion just changed jobs.

Bad hooks: "I noticed you're a customer" or generic industry trends.

Step 5: Generate All Three Formats

Use the strongest hooks to write all three formats. Each format has different constraints and conventions — follow the format-specific guidelines in references/outreach-formats-guide.md.

Always produce all three, clearly labeled.

When the user's company context is available (see references/my-company-context.md), ground the value bridge and pitch in the user's specific product and positioning.

Step 6: Annotate Your Choices

After the three drafts, include a brief note (2–4 sentences) explaining:

  • Which signals were used and why they were chosen

  • Any assumptions made (e.g., inferred call objective)

  • Alternative angles if the primary hook doesn't land

Output Format

## Outreach for [Name / Company]

### 📧 Email

**Subject:** [Subject line]

[Email body — 3–5 sentences]

---

### 📞 Call Script

**Opening:**
[Opening line — conversational, 1–2 sentences]

**Value Bridge:**
[Why you're calling and why now — 2–3 sentences tied to a signal]

**Ask:**
[Single, low-friction ask — e.g., 15-minute call, specific question]

---

### 💼 LinkedIn Message

[Under 300 characters. Warm, personal, no pitch.]

---

### Signal Notes
[2–4 sentences: which signals were used, why, and any alternative angles]

When Signal Data Is Sparse

If Common Room returns minimal data on the target (e.g., just name, title, tags — no activity, no scores, no Spark):

  1. Do not draft outreach from thin air. Outreach grounded in fabricated signals is worse than no outreach.

  2. Run web search first — this becomes your primary personalization source. Look for recent news, LinkedIn posts, conference talks, company announcements.

  3. If web search also returns little, present what you have honestly and ask the user for context:

## Outreach for [Name / Company] — Limited Data

**What I found:**
[Only the real data from CR and web search]

**I don't have enough signal to draft personalized outreach yet.** To write something strong, I'd need:
- Recent activity or engagement signals
- Context you have from prior conversations
- A specific reason for reaching out now

Can you share any of the above?

Quality Standards

  • Every message must reference something specific — generic outreach is not acceptable output

  • Match tone to context: warm and conversational for inbound/community signals; more formal for cold/executive outreach

  • The LinkedIn message must be under 300 characters — no exceptions

  • The call script must be speakable naturally — read it aloud mentally to check rhythm

  • Never fabricate signals — only reference data retrieved from Common Room or web search

Reference Files

  • references/outreach-formats-guide.md — detailed format rules, examples, and tone guidelines for each channel

Requirements and compatibility

Written for: Claude Code, Claude apps

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
Common Room
Publisher
Anthropic (Official)
Distributed by
Anthropic
Source
anthropics/knowledge-work-plugins · partner-built/common-room/skills/compose-outreach · commit e050c2e
Licence
Apache License 2.0 (redistribution allowed)
  • LICENSE (added by AutoGineer from partner-built/common-room/LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Common Room or Anthropic.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download compose-outreach.zip