Token导航 LogoToken导航TokenDH.com
研究检索只读github未标认证来源可访问许可证需确认审计异常

cold-email-sequence-generator-skill冷邮件序列生成器技巧

Agent Skill

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

总安装

245

周安装

10

GitHub Stars

12

下载量

78
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/scientiacapital/skills --skill cold-email-sequence-generator-skill

简介

cold-email-sequence-generator-skill 支持 A/B 变体的冷邮件序列生成。

  • 读取 config.json 判断是否启用变体分配机制,自动标记测试组。
  • 输出包含完整七封邮件模板、主题行、个性化变量与性能基准。
  • 需配合 scripts/variant-assigner.sh 脚本来实现分组逻辑处理。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

Cold Email Sequence Generator

<quick_start> Trigger: "Create a cold email sequence for [audience]" or "Write a 7-email sequence for [use case]" Input: Target audience/ICP, your value proposition, social proof/case studies, sequence length Output: Full email sequence with subject lines (A/B), body copy, timing, personalization variables, and performance benchmarks </quick_start>

<variant_support> This skill supports A/B variants via config.json.

  1. Read this skill's config.json — check if variants.enabled is true
  2. If enabled, run: bash scripts/variant-assigner.sh cold-email-sequence-generator-skill $(date +%s)
  3. Apply the prompt_suffix from the assigned variant's definition to modify the workflow
  4. Record the variant name in the outcome sidecar (see final stage below)

Current experiment: cold-email-subject-style-001

  • control: Standard 7-email framework
  • concise: 5-email framework, 50-word max per email </variant_support>

<success_criteria>

  • Sequence type selected (Classic 7-email, Fast-Track 5, Long-Play 12-14, Event-Based, Re-Engagement)
  • Each email has A/B subject lines, body copy, and clear single CTA
  • Send timing and day/time recommendations included
  • Personalization variables identified with sourcing guidance
  • Social proof integrated (case studies, stats, testimonials)
  • Breakup email included as final touch
  • Performance benchmarks provided for optimization </success_criteria>

Sequence Types

  1. Classic Cold Outreach (7 emails, 2 weeks)
  2. Fast-Track (5 emails, 1 week)
  3. Long-Play Nurture (12-14 emails, 4-6 weeks)
  4. Event/Trigger-Based (3-5 emails, event-specific)
  5. Re-Engagement (5 emails, revive old leads)

Email Sequence Framework

Email #RoleGoalLengthCTA Style
1IntroductionMake them aware you exist50-100 wordsSoft ask (reply, quick question)
2Value ProofEstablish credibility75-125 wordsSpecific meeting time
3Different AngleAddress alternative pain50-75 wordsYes/no question
4Social ProofShow peer validation60-90 wordsSimple reply
5Resource ShareGive before asking40-60 wordsSoft (let me know if helpful)
6Direct AskBe straightforward30-50 wordsDirect meeting request
7BreakupLast attempt + opt-out25-40 words"Should I close your file?"

Timing & Sending

Email #DayTimeExpected Open Rate
1Day 010:00 AM40-50%
2Day 211:00 AM30-40%
3Day 42:00 PM25-35%
4Day 610:30 AM20-30%
5Day 83:00 PM15-25%
6Day 109:00 AM12-20%
7Day 144:00 PM10-18%

Best Practices: Tuesdays-Thursdays highest open rates. 10-11 AM and 2-3 PM optimal. Avoid Mondays (inbox overload) and Fridays (weekend mode). Send in recipient's local timezone.

Email Templates

Email #1: The Introduction

Subject Lines (A/B Test):

  • A (Curiosity): Quick question about [their company]'s [specific challenge]
  • B (Value): [Quantifiable outcome] for [their company type]
  • C (Personal): [Name], saw your post about [specific topic]
Hi [First Name],

I noticed [specific observation about their company/role] and thought you might be facing [specific challenge].

We've helped [similar company 1] and [similar company 2] [achieve specific outcome] without [common objection].

Worth a quick 15-minute conversation to see if we can do the same for [their company]?

Best,
[Your Name]

P.S. - [Personalized one-liner based on research]

Email #2: The Value Proof

Subject: "How [Similar Company] achieved [specific result]"

[First Name],

Following up—wanted to share how this worked for a company like [theirs].

[Similar Company] was [specific situation]. In just [timeframe], they:
- [Specific result #1 with metric]
- [Specific result #2 with metric]
- [Specific result #3 with metric]

The best part? They got started in under [timeframe] without [common objection].

Would [Day] at [Time] work for 15 minutes?

[Your Name]

Email #3: The Different Angle

Subject: "Different thought about [their company]"

Hi [First Name],

I realize [original pain point] might not be top of mind right now.

But what about [alternative pain point]?

Most [their role]s say [common complaint], which is why [mini value prop].

If this hits closer to home, happy to share how [quick win].

[Your Name]

P.S. - If neither is relevant, just let me know and I'll stop!

Email #4: The Social Proof

Subject: "[Mutual connection] suggested I reach out" OR "How [competitor] handles [challenge]"

[First Name],

I was speaking with [name/title] at [similar company] about [challenge].

Here's what they said after implementing [solution]:
"[Direct quote with specific result]"

Open to a quick call to hear more about what's working in [their industry]?

[Your Name]

Email #5: The Resource Share

Subject: "Thought you might find this useful"

[First Name],

No ask here—just sharing something helpful:

[Brief description of resource]: [Link]

We created this after hearing [their role]s struggle with [pain point]. Actionable tips even if you never use our product.

Hope it helps!

[Your Name]

Email #6: The Direct Ask

Subject: "Let's cut to the chase"

[First Name],

Let me be direct: I think we could help [their company] [achieve outcome] based on [observation].

I'd like to show you:
1. [Specific thing #1]
2. [Specific thing #2]
3. [How others in their position use it]

15 minutes. No pressure. How's [specific day/time]?

[Your Name]
[Phone number]

Email #7: The Breakup

Subject: "Should I close your file?"

[First Name],

I'll assume [topic] isn't a priority right now—totally fine.

I'll close your file unless I hear otherwise. For what it's worth, we see best results when [time-sensitive reason], so if you want to revisit, might be worth a quick chat now.

No worries either way—appreciate your time.

[Your Name]

P.S. - If someone else at [their company] should hear about this, happy to redirect.

Breakup Variations:

  • FOMO: "Taking you off the list. FYI—[competitor] just started and is seeing [early result]."
  • Permission: "Assuming this is: 1) Not relevant, 2) Not priority, 3) Bad timing. Which? If #3, when should I check back?"
  • Referral: "Clearly I'm not reaching the right person. Should I talk to someone else about [topic]?"

A/B Testing Strategy

Test Priority (in order):

  1. Subject Lines: Question vs. Statement, Generic vs. Personalized, Short vs. Long
  2. Email Body: Length (50 vs. 100 words), CTA style (Link vs. Question vs. Time slot)
  3. Send Time: Morning vs. Afternoon, Tue vs. Wed vs. Thu

Method: Send to 100 prospects (50/50 split), wait 48 hours, measure open + reply rates, winner goes to remaining list.

Performance Benchmarks

MetricGoodGreatExceptional
Email 1 Open Rate35-45%45-55%55%+
Email 1 Reply Rate3-8%8-15%15%+
Sequence Reply Rate8-15%15-25%25%+
Positive Reply %40-50%50-70%70%+
Meeting Booked %1-3%3-6%6%+

Segmentation

Adjust sequences by Industry (swap case studies, use industry terminology), Company Size (Startup: ROI focus; Mid-Market: scalability; Enterprise: security/compliance), Role (Executive: strategic outcomes; Practitioner: time savings; Technical: architecture/specs), and Intent (Hot: shorter/faster; Warm: standard 7-email; Cold: longer nurture).

Quick-Start Templates

SaaS Sales: Question about growth metric → Competitor case study → Alternative pain → Mutual connection → Free benchmark report → 15-min demo → Close file

Agency/Services: Recent achievement → Client case study → Quick idea for challenge → Competitor approach → No-strings audit → 15-min call → Bad timing?

Partnership: Mutual contact intro → Win-win opportunity → Similar partner example → Partnership program question → Worth exploring?

Pro Tips

  1. 3-Second Rule: Prospect should understand value in first 3 seconds
  2. One CTA Only: Don't give multiple options
  3. Mobile-First: 50%+ opened on mobile; keep scannable
  4. No Attachments: Use links; attachments trigger spam filters
  5. The P.S. Works: PostScripts get read; use for secondary CTA
  6. Follow-Up Matters: 80% of responses come from emails 3-7

Pre-Launch Checklist

  • Sender email has good deliverability (SPF, DKIM, DMARC)
  • Email warmed up (sent successful emails recently)
  • List cleaned (no invalid emails)
  • Personalization variables all filled
  • Links tested and tracked
  • CRM integration working
  • A/B tests configured
  • Daily send limits set (avoid spam flags)

Emit Outcome Sidecar

As the final step, write to ~/.claude/skill-analytics/last-outcome-cold-email-sequence-generator.json:

{"ts":"[UTC ISO8601]","skill":"cold-email-sequence-generator","version":"1.1.0",
 "variant":"[assigned variant or default]","status":"[success|partial|error]",
 "runtime_ms":[estimated ms from start],
 "metrics":{"sequences_created":1,"emails_generated":[count],"subject_variants_generated":[count]},
 "error":null,"session_id":"[YYYY-MM-DD]"}

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

38.81%
按下载量换算30

Claude

30.77%
按下载量换算24

Cursor

17.18%
按下载量换算13

Gemini CLI

10.45%
按下载量换算8

安全审计

Gen Agent Trust Hub

未通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills