compose-outreach
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.
Best use case
compose-outreach is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using compose-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/compose-outreach/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How compose-outreach Compares
| Feature / Agent | compose-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?
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.
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
AI Agent for Cold Email Generation
Discover AI agent skills for cold email generation, outreach copy, lead personalization, CRM support, and sales-adjacent messaging workflows.
AI Agents for Freelancers
Browse AI agent skills for freelancers handling client research, proposals, outreach, delivery systems, documentation, and repeatable admin work.
AI Agents for Marketing
Discover AI agents for marketing workflows, from SEO and content production to campaign research, outreach, and analytics.
SKILL.md Source
# 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
Related Skills
draft-outreach
Research a prospect then draft personalized outreach. Uses web research by default, supercharged with enrichment and CRM. Trigger with "draft outreach to [person/company]", "write cold email to [prospect]", "reach out to [name]".
pipeline-review
Analyze pipeline health — prioritize deals, flag risks, get a weekly action plan. Use when running a weekly pipeline review, deciding which deals to focus on this week, spotting stale or stuck opportunities, auditing for hygiene issues like bad close dates, or identifying single-threaded deals.
forecast
Generate a weighted sales forecast with best/likely/worst scenarios, commit vs. upside breakdown, and gap analysis. Use when preparing a quarterly forecast call, assessing gap-to-quota from a pipeline CSV, deciding which deals to commit vs. call upside, or checking pipeline coverage against your number.
daily-briefing
Start your day with a prioritized sales briefing. Works standalone when you tell me your meetings and priorities, supercharged when you connect your calendar, CRM, and email. Trigger with "morning briefing", "daily brief", "what's on my plate today", "prep my day", or "start my day".
create-an-asset
Generate tailored sales assets (landing pages, decks, one-pagers, workflow demos) from your deal context. Describe your prospect, audience, and goal — get a polished, branded asset ready to share with customers.
competitive-intelligence
Research your competitors and build an interactive battlecard. Outputs an HTML artifact with clickable competitor cards and a comparison matrix. Trigger with "competitive intel", "research competitors", "how do we compare to [competitor]", "battlecard for [competitor]", or "what's new with [competitor]".
call-summary
Process call notes or a transcript — extract action items, draft follow-up email, generate internal summary. Use when pasting rough notes or a transcript after a discovery, demo, or negotiation call, drafting a customer follow-up, logging the activity for your CRM, or capturing objections and next steps for your team.
update
Sync tasks and refresh memory from your current activity. Use when pulling new assignments from your project tracker into TASKS.md, triaging stale or overdue tasks, filling memory gaps for unknown people or projects, or running a comprehensive scan to catch todos buried in chat and email.
task-management
Simple task management using a shared TASKS.md file. Reference this when the user asks about their tasks, wants to add/complete tasks, or needs help tracking commitments.
memory-management
Two-tier memory system that makes Claude a true workplace collaborator. Decodes shorthand, acronyms, nicknames, and internal language so Claude understands requests like a colleague would. CLAUDE.md for working memory, memory/ directory for the full knowledge base.
write-spec
Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.
synthesize-research
Synthesize user research from interviews, surveys, and feedback into structured insights. Use when you have a pile of interview notes, survey responses, or support tickets to make sense of, need to extract themes and rank findings by frequency and impact, or want to turn raw feedback into roadmap recommendations.