跳到正文
cccskills
免费在 GitHub 公开

outreach-playbook

Run cold outreach that gets replies: research the account, write a short specific first message, and follow up on a fixed schedule without nagging.

中文简介正在准备中。当前显示原文说明。

实测评分 未实测

查看安装方法

包含的文件(1)

  • SKILL.md2.0 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Outreach playbook

Use this for any first contact with someone who did not ask to hear from us.

Before writing anything

Spend the research effort on one question: what changed for this account recently that makes now the moment? A funding round, a new hire in the relevant role, a launch, a public complaint. Outreach with no trigger reads as a mail-merge because it is one.

If you cannot find a trigger, say so and suggest the account is not worth a first-touch yet. Volume is not the goal.

The first message

Four sentences, in this order, and no more:

  1. The trigger, stated as a fact about them.
  2. What that usually causes — the problem, in their words, not ours.
  3. One sentence on what we did about it for someone comparably sized.
  4. A question that is answerable in one line.

Rules that matter more than they look:

  • No greeting beyond their first name; no "I hope this finds you well".
  • Never ask for a 30-minute call in the first message. Ask a question.
  • One link at most, and only if it answers the question you just asked.
  • Subject line is the trigger, lowercase, under six words.

Following up

Three follow-ups, then stop and mark the account dormant for a quarter.

  • Day 3: forward your own message with one new fact, not a nudge.
  • Day 8: a different angle on the same problem. Never "just bumping this".
  • Day 17: one line closing the loop and giving them an easy out.

A reply of "not now" ends the sequence. Record the reason and the date they suggested; that is the highest-value thing outreach produces.

What not to do

Never claim a mutual connection, a prior conversation, or a result you cannot name the customer for. Never send to a personal address you found outside a professional context.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.

中文简介正在准备中。当前显示原文说明。

Significant-Gravitas/skills-catalog22026年10月22日 更新

Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.

中文简介正在准备中。当前显示原文说明。

Significant-Gravitas/skills-catalog22026年10月22日 更新

Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.

中文简介正在准备中。当前显示原文说明。

Significant-Gravitas/skills-catalog22026年10月22日 更新

Write ad variants that each test one idea, within platform limits and supported claims.

中文简介正在准备中。当前显示原文说明。

Significant-Gravitas/skills-catalog22026年10月22日 更新

Use on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.

中文简介正在准备中。当前显示原文说明。

Significant-Gravitas/skills-catalog22026年10月22日 更新

Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.

中文简介正在准备中。当前显示原文说明。

Significant-Gravitas/skills-catalog22026年10月22日 更新

查看 Significant-Gravitas 的全部技能

报告此技能的问题