Compose Outreach

作者 anthropicsae1513ea94dc无许可证27K 个星标收录于 2026年10月8日更新于 2026年10月8日仓库今天更新

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.

AI 生成的概览

根据 Common Room 信号,生成邮件、电话话术和 LinkedIn 消息三种个性化外联草稿。

功能
该技能针对目标公司或联系人产出三种带标签的外联草稿:含主题行的邮件、包含开场、价值衔接和请求的电话话术,以及不超过 300 字符的 LinkedIn 消息。它从 Common Room 信号中提取个性化切入点,必要时用网络搜索或 Spark 补充信息,并附上简短说明解释所用信号。当信号数据稀少时,它不会凭空起草,而是向用户询问背景信息。
适用场景
适用于被要求向特定个人或公司起草外联内容、给指定联系人写邮件,或为潜在客户撰写消息的场景。适合需要以互动和意向信号为依据进行个性化的销售或社区驱动型外联。
运行要求
需要 Common Room MCP 工具进行信号查询,可选使用 Spark 补充信息和网络搜索。它会引用格式指南和公司背景文件。不附带脚本,仅为指令。

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

来源与署名

来源:anthropics/knowledge-work-plugins位于partner-built/common-room/skills/compose-outreach提交ae1513e

许可证: 无许可证

内容归原作者所有。SourceWeft 从公开仓库中收录这些内容。

举报或申请下架

更多来自 anthropics/knowledge-work-plugins 的技能

Ticket Deflector

anthropics

精选

Reads a forwarded customer email or ticket, pulls order and refund status from a payments connector (PayPal, Square, or Stripe) or Shopify, account history from the CRM, and open tickets from a support desk (Zoho Desk), drafts a tone-matched reply in the owner's writing voice, and can issue a refund through the payments connector with explicit owner approval. With Shopify connected it also runs a proactive order-triage mode that surfaces orders needing attention — unfulfilled past the promised window, payment problems, pending refunds, stuck shipments — and drafts the next action for each before the customer has to ask. Use when the user says "draft a response," "answer this customer," "where's my order," "I want a refund," "check my orders," or "anything about to blow up."

待分类27K今天更新

Tax Season Organizer

anthropics

精选

Prepares tax-season materials for the owner's accountant, not tax advice. US federal tax; a non-US business gets its closed-books packet instead. Two modes: (1) quarterly estimated tax from YTD net income in the ledger (MYOB, NetSuite, QuickBooks, Xero, or Zoho Books); (2) year-end 1099 prep, scanning the ledger, PayPal, and Stripe for contractors paid over USD 600 into a 1099-NEC list with missing W-9 flags. Any tax request routes first to /tax-prep, which confirms the books are closed and reconciled before running this skill. Use this skill directly only when the owner says the period's books are already closed: "books are closed, now do the 1099s," "run the quarterly estimate off the closed numbers," or "just the contractor W-9 list."

待分类27K今天更新

Tax Prep

anthropics

精选

基于已结账的账目准备税务材料:季度预估缴税明细,或年终 1099-NEC 清单与会计师资料包。

Business & Finance27K今天更新

Smb Onboard

anthropics

精选

引导小微企业主完成首次设置:连接工具、运行一次体现价值的配方、记录业务背景并设定每周检查节奏。

Productivity & Workflow27K今天更新

Smb Router

anthropics

精选

将小企业主的需求转接到合适的插件技能或命令,并说明可用功能。

Productivity & Workflow27K今天更新

Month End Prep

anthropics

精选

Reconciles the accounting ledger (MYOB, NetSuite, QuickBooks, Xero, or Zoho Books) against PayPal, Shopify, Square, and Stripe settlements, flags transactions that need attention, suspicious duplicates, and missing receipts, then writes a plain-English P&L narrative and exports a close packet (xlsx + one-page PDF). This is the first link of the /close-month command; a request to close the month or the books routes there, and the command runs this skill before refreshing the forecast and distributing the packet. Use this skill directly only when the owner wants the reconciliation alone, with no forecast refresh and no distribution: "just reconcile, no packet," "what's missing from the books," "flag the duplicates and missing receipts," or "write the P&L narrative for this month."

待分类27K今天更新