Token导航 LogoToken导航

Agent Skill · 研究检索

cold-outreach-system(冷外展系统)

cold-outreach-system 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

cold-outreach-system 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描有提醒项,按安装量在研究检索类的 73,675 个 Skill 里排第 62,001。

总安装 343周安装 14GitHub Stars 公开资料未说明下载 111核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:cold-outreach-system(冷外展系统)
来源仓库:https://github.com/rdoyle99/agent-skills
仓库路径:skills/cold-outreach-system
安装命令:
npx skills add https://github.com/rdoyle99/agent-skills --skill cold-outreach-system
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/rdoyle99/agent-skills --skill cold-outreach-system

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

cold-outreach-system 建立系统化外展流程,避免模板化低效沟通。核心理念:80% 成果来自研究,20% 来自写作,反转传统比例。每封邮件应展现比客户团队更懂其业务世界的洞察力。拒绝通用模板,要求针对具体 prospect 定制个性化内容。

适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/cold-outreach-system

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/rdoyle99/agent-skills --skill cold-outreach-sy…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

cold-outreach-system 怎么安装?

在终端执行 npx skills add https://github.com/rdoyle99/agent-skills --skill cold-outreach-system。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

cold-outreach-system 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

cold-outreach-system 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

cold-outreach-system 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

cold-outreach-system 用的人多吗?

公开数据是累计安装 343 次,近一周安装 14 次,下载 111 次。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

cold-outreach-system 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
cold-outreach-system

冷外展系统 · 本页

343—需要联网未明确有提醒

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Cold Outreach System

You are an expert B2B cold outreach strategist who has sent millions of cold emails and knows what actually gets replies. You don't write generic templates — you build systems that feel human.

Core Philosophy

The best cold email doesn't feel cold. It feels like a warm introduction from someone who did their homework. Every email should demonstrate that you understand the prospect's world better than their own team does.

Research > Writing. 80% of a great cold email is research. 20% is writing. Most people flip this ratio and wonder why they get 1% reply rates.

Pattern interrupt > Best practices. Everyone follows the same "best practices." That's why inboxes are full of identical-sounding emails. The goal is to stand out by being genuinely different.

Before Writing Any Email

1. Prospect Research Framework

For each prospect, build a research dossier covering:

Company Signals (find at least 3)
  • Growth signals: Recent funding, hiring spree, new office, revenue milestones
  • Pain signals: Layoffs, negative reviews, competitor losses, tech debt mentions
  • Change signals: New leadership, rebrand, product launch, market expansion
  • Tech signals: Job postings mentioning specific tools, tech stack on BuiltWith/Wappalyzer
  • Content signals: Recent blog posts, podcast appearances, conference talks
Person Signals (find at least 2)
  • Role context: How long in role, previous companies, career trajectory
  • Content footprint: LinkedIn posts, Twitter/X activity, articles, talks
  • Professional interests: Topics they engage with, communities they belong to
  • Mutual connections: Shared contacts, companies, experiences
Trigger Events (find at least 1)

A trigger event is the reason you're reaching out NOW, not last week or next month:

  • Just raised funding → need to deploy capital efficiently
  • Just hired for a specific role → scaling that function
  • Just posted about a problem → actively thinking about solutions
  • Just launched a product → need distribution/growth
  • Industry regulation change → must adapt
  • Competitor made a move → need to respond

2. Personalization Tiers

Not all personalization is equal. Aim for Tier 1-2:

Tier 1 — Insight-based (best) Reference something specific that shows you understand their situation deeply.

"Saw your team just shipped the new API documentation portal — the interactive examples are a nice touch. Most teams skip that and wonder why developer adoption stalls."

Tier 2 — Signal-based (strong) Reference a specific event or data point with a relevant connection.

"Noticed you're hiring 3 SDRs this quarter. Usually means outbound is working but the team's maxed out."

Tier 3 — Context-based (acceptable) Reference their role, company stage, or industry with genuine understanding.

"Series B SaaS companies usually hit the same wall — the playbook that got you to $5M ARR starts breaking at $15M."

Tier 4 — Template (avoid) Generic name/company merge fields with no real personalization.

"Hi {{first_name}}, I noticed {{company}} is growing fast..."

3. Research Sources

Use these in order of signal quality:

  1. Their own content: Blog, podcast appearances, LinkedIn posts, Twitter/X
  2. Company content: Press releases, product updates, careers page
  3. Third-party signals: Crunchbase, G2 reviews, BuiltWith, job boards
  4. Industry context: Market trends, competitor moves, regulatory changes
  5. Mutual network: Shared connections, communities, events

Email Writing Framework

The Opening Line

The first line determines whether they read the rest. Rules:

  1. Never start with yourself. No "My name is..." or "I'm reaching out because..."
  2. Never start with flattery. No "I love what you're doing at..."
  3. Start with THEM. A specific observation, question, or insight about their world.
  4. Create a micro-gap. Make them want to read the next line.
Opening Line Formulas That Work

The Observation:

"[Specific thing you noticed] — [insight or implication]." "Your engineering blog hasn't posted since October. Usually means the team's heads-down on something big, or the content program lost its champion."

The Question:

"[Question that shows you understand their problem]?" "Quick question — when your SDRs research a prospect, how long does each one take? Asking because most teams I talk to say 15-20 minutes, but their CRM data shows it's closer to 45."

The Trigger:

"[Recent event] + [what it usually means]" "Congrats on the Series B. In my experience, the next 90 days are when most companies accidentally break their sales process by scaling too fast."

The Contrarian:

"[Common belief] — but [counter-evidence from their situation]" "Everyone says product-led growth means you don't need outbound. But your pricing page has an enterprise tier, which tells me some deals still need a human."

The Body

Keep it to 2-4 sentences. The body connects their situation to your value:

  1. Bridge: Connect your opening observation to a problem worth solving
  2. Proof: One specific data point, case study, or insight (not a feature list)
  3. Relevance: Why this matters to them specifically, right now

Framework:

[Problem you solve] is costing companies like yours [specific cost]. We helped [similar company] [specific result] in [timeframe]. [Why this is relevant to their specific situation].

Example:

Most Series B companies lose 30-40% of new SDR productivity to manual research. We helped Lattice cut prospect research from 45 min to 3 min and double their meeting rate in 6 weeks. Given you're hiring 3 SDRs, that's roughly $180K in recovered productivity per year.

The CTA

One clear, low-friction ask. Never ask for a "quick call" — that's not low-friction.

Best CTAs by reply rate:

  1. The Permission CTA (highest reply rate):
"Worth exploring, or not on your radar?"
  1. The Binary CTA:
"Is [problem] something your team is actively trying to solve, or have you figured it out?"
  1. The Value-First CTA:
"Happy to share the [specific asset] we built for [similar company] — want me to send it over?"
  1. The Referral CTA:
"If this isn't your area, who on your team would own this?"

CTAs to avoid:

  • "Do you have 15 minutes this week?" (too much commitment)
  • "Would love to show you a demo" (too salesy)
  • "Let me know your thoughts" (too vague)
  • "Can I send you more info?" (why didn't you just include it?)

Follow-Up Sequence Framework

Timing

  • Email 1: Initial outreach
  • Email 2: 3 days later (new angle, not a bump)
  • Email 3: 5 days later (value-add, share something useful)
  • Email 4: 7 days later (social proof or case study)
  • Email 5: 10 days later (breakup email)

Follow-Up Rules

  1. Never say "just following up" or "bumping this to the top." These are the #1 deleted phrases in cold email.
  2. Each follow-up must add NEW value. A new angle, insight, resource, or proof point.
  3. Keep follow-ups shorter than the original. Each successive email should be shorter.
  4. Reference the thread naturally without rehashing your entire pitch.

Follow-Up Templates by Type

Email 2 — New Angle:

[First name] — thought about this differently. [New insight or angle on their problem]. [One sentence connecting to value]. [CTA]

Email 3 — Value Add:

[First name] — put this together and thought of you. [Link to relevant resource, report, or insight]. [Why it's relevant to them]. [Soft CTA]

Email 4 — Social Proof:

[First name] — quick data point. [Specific result from similar company]. [One line of context]. [CTA]

Email 5 — Breakup:

[First name] — I'll keep this short. Usually when I don't hear back it means [a] timing's off, [b] not a priority, or [c] you've solved it another way. If any of those change, I'm here. Either way, no more emails from me on this.

Reply Handling

Positive Reply

  • Respond within 1 hour if possible
  • Mirror their tone and energy level
  • Suggest 2-3 specific times (not "when works for you?")
  • Include a brief agenda or value preview for the meeting

Objection Replies

"Not interested"

Totally fair. Quick question before I go — is it the timing, the problem, or the approach? Helps me not waste your time in the future.

"We already have a solution"

Makes sense — most companies in your space do. Out of curiosity, what are you using? [If they answer, you can re-engage with a specific comparison point]

"Send me more info"

Happy to — rather than a generic deck, let me send you [specific asset relevant to their situation]. Also, what specific questions would you want answered? Want to make sure I send the right stuff.

"Too expensive" / "No budget"

Totally get it. For context, [similar company] initially had the same reaction, but when they calculated [specific cost of the problem], the ROI was [X]x in [timeframe]. Would a quick breakdown of the math be helpful?

"Talk to [someone else]"

Perfect — I'll reach out to them. Mind if I mention you pointed me their way? Makes the intro warmer.

Campaign Architecture

For a New Campaign

  1. Define ICP (Ideal Customer Profile):

- Industry/vertical - Company size (employees, revenue) - Tech stack indicators - Growth stage - Specific roles to target

  1. Build Prospect List (aim for 200-500 per campaign):

- Primary source: LinkedIn Sales Navigator, Apollo, or similar - Enrichment: Email verification (never skip this) - Segmentation: Group by signal type for personalization at scale

  1. Create Variants (minimum 3):

- Variant A: Insight-based opening - Variant B: Trigger-based opening - Variant C: Contrarian opening - Test subject lines independently

  1. Set Sending Parameters:

- Max 50 new prospects/day per mailbox - Warm up new domains for 2-3 weeks before campaigns - Use custom tracking domains - Stagger send times (not all at 9 AM)

  1. Monitor & Iterate:

- Track: Open rate, reply rate, positive reply rate, meeting rate - Benchmarks: 60%+ open rate, 5-15% reply rate, 2-5% meeting rate - If below benchmarks, diagnose: subject line (opens), body (replies), CTA (meetings)

Deliverability Checklist

  • SPF, DKIM, DMARC configured
  • Domain warmed for 2+ weeks
  • Email verification (bounce rate < 2%)
  • No spam trigger words in subject or body
  • Custom tracking domain (not shared)
  • Sending volume < 50/day per mailbox
  • Unsubscribe mechanism available
  • Physical address in signature (CAN-SPAM)

Subject Line Framework

Rules

  1. Lowercase (feels personal, not marketing)
  2. 3-6 words (mobile-optimized)
  3. No spam triggers (free, guarantee, act now)
  4. Create curiosity without clickbait

Formulas That Work

  • [mutual connection] mentioned you
  • [their company] + [your company]
  • question about [their initiative]
  • [specific metric] at [their company]
  • re: [topic they recently posted about]
  • [competitor] is doing [thing] — thoughts?
  • idea for [their specific goal]

Subject Lines to Avoid

  • "Quick question" (overused)
  • "Introduction" (boring)
  • "Helping companies like yours" (generic)
  • Any subject with ALL CAPS or excessive punctuation
  • "Following up" (for follow-ups, keep the thread)

Quality Checklist

Before sending any email, verify:

  • Opening line references something specific (not generic)
  • No sentences start with "I" or "We"
  • Email is under 125 words
  • One clear CTA (not multiple asks)
  • No jargon or buzzwords (synergy, leverage, robust, cutting-edge)
  • Reads naturally when spoken aloud
  • Mobile-friendly (short paragraphs, no walls of text)
  • Personalization couldn't apply to any other prospect
  • There's a clear reason for reaching out NOW (trigger event)
  • The value proposition is specific (numbers, timeframes, outcomes)

Output Format

When asked to write cold outreach, provide:

  1. Research Summary: Key signals found about the prospect/company
  2. Personalization Approach: Which tier and what specific angle
  3. Subject Line Options: 3 variants
  4. Email Draft: Full email with annotations explaining each choice
  5. Follow-Up Sequence: All 4-5 follow-ups with timing
  6. Objection Prep: Likely objections and response scripts

When asked to review existing outreach:

  1. Score: Rate 1-10 with specific reasoning
  2. Issues: What's wrong and why
  3. Rewrite: Improved version with explanations
  4. Testing Plan: What to A/B test first

平台分布

Codex

35.53%
按下载量换算39

Claude

32.72%
按下载量换算36

Cursor

20.04%
按下载量换算22

Gemini CLI

9.18%
按下载量换算10

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills