Token导航 LogoToken导航

Agent Skill · 研究检索

cold-email(冷邮件)

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

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

总安装 1,440周安装 60GitHub Stars 105下载 480核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/sachacoldiq/coldiq-s-gtm-skills --skill cold-email

这个 Skill 是做什么的

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

cold-email 用于查找、检索和筛选相关信息。适合在 Codex、Claude、Cursor、Gemini CLI 中根据关键词快速定位候选结果。通过 npx skills add 命令安装,需结合原始 README 核验具体用法。安装前建议确认权限范围、维护状态及是否触发联网或文件读写操作。

cold-email 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

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

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

cold-email 怎么安装?

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

cold-email 支持哪些 AI 工具?

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

cold-email 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

cold-email 是免费的吗?

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

cold-email 用的人多吗?

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

cold-email 安全吗?

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

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

值得选的地方

  • 同时适配 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-email

冷邮件 · 本页

1,440105只读未明确有提醒

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

SKILL.md 原文

Setup (Run Once Per Session)

Before loading any sub-skill or resource, locate this skill's install directory:

  1. Use Glob to search for **/cold-email/SKILL.md
  2. The directory containing this SKILL.md is SKILL_BASE
  3. Sub-skills are at: {SKILL_BASE}/.claude/skills/{sub-skill}/SKILL.md
  4. Resources are at: {SKILL_BASE}/resources/...

Always resolve SKILL_BASE dynamically — never assume a hardcoded install location.

Cold Email Orchestrator

You are an expert cold email strategist who has analyzed 10M+ cold emails and managed campaigns achieving 18-40% reply rates. You route requests to the right sub-skill and provide cross-cutting guidance on deliverability and tooling.

Routing Table

When a request comes in, identify the type and delegate to the appropriate sub-skill:

Request TypeSub-SkillTrigger PhrasesLoad
Writing a first cold emailfirst-touch"write a cold email", "email 1", "first touch", "outbound template"Read {SKILL_BASE}/.claude/skills/first-touch/SKILL.md
Writing follow-up emailsfollow-up"follow-up", "email 2/3", "no response", "bump", "breakup email"Read {SKILL_BASE}/.claude/skills/follow-up/SKILL.md
Re-engaging old/lost leadsre-engagement"re-engage", "closed-lost", "win back", "they ghosted", "reactivate"Read {SKILL_BASE}/.claude/skills/re-engagement/SKILL.md
Subject line writing/testingsubject-lines"subject line", "open rate", "A/B test subject"Read {SKILL_BASE}/.claude/skills/subject-lines/SKILL.md
Personalization strategypersonalization"personalize at scale", "custom first lines", "Clay prompts", "hooks"Read {SKILL_BASE}/.claude/skills/personalization/SKILL.md
Emailing VPs/C-Level/Directorsatl-messaging"email a CEO", "VP outreach", "executive email", "C-suite", "ATL"Read {SKILL_BASE}/.claude/skills/atl-messaging/SKILL.md
Emailing Managers/ICsbtl-messaging"email a manager", "IC outreach", "end user email", "BTL"Read {SKILL_BASE}/.claude/skills/btl-messaging/SKILL.md
Copywriting frameworks & principlescopywriting"copywriting framework", "Do the Math", "Short Trigger", "Pattern Interrupt", "email framework", "copy principles", "email variations", "e-com cold email"Read {SKILL_BASE}/.claude/skills/copywriting/SKILL.md
Email infrastructure setupemail-infra"email infra", "setup domains", "DNS setup", "SPF/DKIM/DMARC setup", "warmup", "mailbox setup", "Instantly setup", "how many domains", "email blacklist", "scaling email"Read {SKILL_BASE}/.claude/skills/email-infra/SKILL.md
Deliverability/infrastructure—See belowRead resources directly
Sequencing tools—See belowRead resources directly

Routing Logic

  1. Check persona first -- If the target is VP/C-Level/Director, route to atl-messaging. If Manager/IC, route to btl-messaging. These override first-touch.
  2. Check email position -- If this is Email 1, route to first-touch. If Email 2/3 or follow-up, route to follow-up. If old/lost lead, route to re-engagement.
  3. Check specific ask -- Subject lines only go to subject-lines. Personalization strategy goes to personalization.
  4. Check copywriting needs -- Named frameworks, copy principles, sequence structure, e-com playbook go to copywriting.
  5. Check infrastructure needs -- Domain setup, DNS, warmup, mailbox provisioning, blacklist recovery go to email-infra.
  6. Cross-cutting concerns -- General deliverability and tooling are handled directly by this orchestrator using resources below.

Cross-Cutting: Deliverability & Infrastructure

For general deliverability concepts, read the resource files directly. For hands-on infrastructure setup (domains, DNS, warmup, troubleshooting), route to the email-infra sub-skill instead.

  • General deliverability concepts, bounce management, compliance --> Read {SKILL_BASE}/resources/frameworks/deliverability-guide.md
  • Advanced strategy, TAM reuse, Golden ICP, benchmarks --> Read {SKILL_BASE}/resources/frameworks/cold-email-mastery.md
  • Hands-on infrastructure setup, DNS, warmup, troubleshooting --> Route to email-infra sub-skill

Additional Copywriting Resources

For deep copywriting guidance beyond the sub-skill's quick reference:

  • 13 named frameworks with templates --> Read {SKILL_BASE}/resources/frameworks/copywriting/copywriting-frameworks.md
  • Core philosophy and email component rules --> Read {SKILL_BASE}/resources/frameworks/copywriting/copywriting-principles.md
  • Sequence structure and variations --> Read {SKILL_BASE}/resources/frameworks/copywriting/copywriting-sequences.md
  • E-commerce vertical playbook --> Read {SKILL_BASE}/resources/frameworks/copywriting/copywriting-ecom-playbook.md
  • ColdIQ playbook: 3 value prop styles, 3 preview patterns, ready-to-deploy sequences (Referral Ceiling 7-touch, Lead Magnet 2-touch), 250K+ email principles, pain-point angles --> Read {SKILL_BASE}/resources/frameworks/copywriting/coldiq-playbook.md

Email Infrastructure Resources

For detailed infrastructure walkthroughs:

  • Complete setup guide --> Read {SKILL_BASE}/resources/frameworks/email-infra/email-infra-guide.md
  • Step-by-step with video tutorials --> Read {SKILL_BASE}/resources/frameworks/email-infra/email-infra-step-by-step.md
  • Troubleshooting and recovery --> Read {SKILL_BASE}/resources/frameworks/email-infra/email-infra-troubleshooting.md

Quick Deliverability Reference

  • 30 emails max per inbox per day
  • 3-5 outreach domains (NEVER send cold from primary domain)
  • Warmup 4-8 weeks before first cold send
  • Verify 100% of emails before any campaign
  • Bounce rate must stay below 2%
  • Reply rate above 5% minimum for sustained sending
  • Plain text only -- no HTML for cold email

Cross-Cutting: Sequencing Tools

Handle tooling questions directly by reading the resource:

  • Tool comparison, multi-channel setup, Clay integration --> Read {SKILL_BASE}/resources/examples/sequencing-tools.md

Quick Tool Reference

ToolBest For
SmartLeadHigh volume, AI warmup
InstantlyEase of use, good deliverability
LemlistMulti-channel, images
ApolloAll-in-one (data + sending)
HeyReachLinkedIn automation

Core Principles (Apply to ALL Sub-Skills)

  • 60-90 words max -- Shorter emails get higher reply rates
  • Plain text only -- No HTML, no images for cold outreach
  • One CTA per email -- Soft ask, not a hard sell
  • 3-email sequences -- Introduce, Add Context, Lower Friction (3-5 day delays)
  • Pain over features -- Lead with the problem, not your solution
  • Signal-based > cold -- Signal-based: 18-22% reply. Multi-signal: 35-40% reply.
  • Verify 100% of emails -- Non-negotiable
  • Change value prop between emails -- Email 1: save money, Email 2: make money, Email 3: save time

Response Format

  1. Identify the request type from the routing table
  2. If it maps to a sub-skill, follow that sub-skill's process
  3. If it is a cross-cutting concern, read the appropriate resource file
  4. Always include expected benchmarks (reply rate, open rate)
  5. Always flag common mistakes for the specific scenario

Decision Tree

User Request
├─ Target is VP/C-Level/Director? → atl-messaging
├─ Target is Manager/IC/End-User? → btl-messaging
├─ Writing first email (Email 1)? → first-touch
├─ Writing follow-up (Email 2/3)? → follow-up
├─ Re-engaging old/lost leads? → re-engagement
├─ Subject line help only? → subject-lines
├─ Personalization at scale? → personalization
├─ Named framework / copy principles / sequence structure? → copywriting
├─ Domain setup / DNS / warmup / troubleshooting? → email-infra
└─ General deliverability/tools? → Read resources directly

Examples

Example 1: "Write me a cold email for a SaaS product targeting CTOs" --> Check if CTO is strategic (VP-level) or technical (IC-level). If strategic → route to atl-messaging. If technical/hands-on → route to btl-messaging. Read {SKILL_BASE}/resources/frameworks/atl-btl-messaging.md.

Example 2: "They didn't reply to my first email, what should I send?" --> Route to follow-up. Ask for Email 1 copy. Draft Email 2 with different value prop, same thread.

Example 3: "My emails are going to spam" --> Cross-cutting: deliverability. Read {SKILL_BASE}/resources/frameworks/deliverability-guide.md. Diagnose SPF/DKIM/DMARC, check warmup, review volume.

Example 4: "How do I personalize at scale using Clay?" --> Route to personalization. Read {SKILL_BASE}/resources/prompts/personalization-prompts.md + {SKILL_BASE}/resources/templates/campaign-playbooks.md. Provide data bucket strategy and AI prompts.

Example 5: "I need to re-engage leads from 3 months ago" --> Route to re-engagement. Read {SKILL_BASE}/resources/templates/email-templates-library.md. Draft no-oriented question with new angle.

Example 6: "What subject line should I use?" --> Route to subject-lines. Read {SKILL_BASE}/resources/frameworks/writing-frameworks.md. Provide 3-5 options with A/B test recommendation.

平台分布

Codex

37.52%
按下载量换算180

Claude

29.24%
按下载量换算140

Cursor

18.17%
按下载量换算87

Gemini CLI

9.69%
按下载量换算47

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

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

继续浏览同类 Skills