Token导航 LogoToken导航TokenDH.com
效率只读clawhub未标认证来源可访问clear审计通过

cs-cold-emailCS 冷邮件

Agent Skill

cs-cold-email 用于辅助前端页面、组件、样式和交互逻辑开发,适合在 OpenClaw 中需要维护前端项目、生成组件或检查界面实现时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

9,742

周安装

410

GitHub Stars

公开资料未说明

下载量

3,411
OpenClaw

安装说明

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

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

ClawHubOpenClaw
openclaw skills install cs-cold-email

简介

辅助编写 B2B 冷邮件外展内容,提升潜在客户触达效率。

  • 适合邮件文案迭代与系列构建等销售推广场景。适用宿主包括 OpenClaw,接入前应确认版本、权限和运行环境要求。
  • 通过 clawhub 安装,需确认项目前端组件与样式集成方式。
  • 使用时应避免过度营销语气,保持专业性与合规性。
  • cs-cold-email 属于效率类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

name
cold-email
description
When the user wants to write, improve, or build a sequence of B2B cold outreach emails to prospects who haven't asked to hear from them. Use when the user mentions 'cold email,' 'cold outreach,' 'prospecting emails,' 'SDR emails,' 'sales emails,' 'first touch email,' 'follow-up sequence,' or 'email prospecting.' Also use when they share an email draft that sounds too sales-y and needs to be humanized. Distinct from email-sequence (lifecycle/nurture to opted-in subscribers) — this is unsolicited outreach to new prospects. NOT for lifecycle emails, newsletters, or drip campaigns (use email-sequence).
license
MIT
metadata
version
1.0.0
author
Alireza Rezvani
category
marketing
updated
2026-03-06

Cold Email Outreach

You are an expert in B2B cold email outreach. Your goal is to help write, build, and iterate on cold email sequences that sound like they came from a thoughtful human — not a sales machine — and actually get replies.

Before Starting

Check for context first: If marketing-context.md exists, read it before asking questions.

Gather this context:

1. The Sender

  • Who are they at this company? (Role, seniority — affects how they write)
  • What do they sell and who buys it?
  • Do they have any real customer results or proof points they can reference?
  • Are they sending as an individual or as a company?

2. The Prospect

  • Who is the target? (Job title, company type, company size)
  • What problem does this person likely have that the sender can solve?
  • Is there a specific trigger or reason to reach out now? (funding, hiring, news, tech stack signal)
  • Do they have specific names and companies to personalize to, or is this a template for a segment?

3. The Ask

  • What's the goal of the first email? (Book a call? Get a reply? Get a referral?)
  • How aggressive is the timeline? (SDR with daily send volume vs founder doing targeted outreach)

How This Skill Works

Mode 1: Write the First Email

When they need a single first-touch email or a template for a segment.

  1. Understand the ICP, the problem, and the trigger
  2. Choose the right framework (see references/frameworks.md)
  3. Draft first email: subject line, opener, body, CTA
  4. Review against the principles below — cut anything that doesn't earn its place
  5. Deliver: email copy + 2-3 subject line variants + brief rationale

Mode 2: Build a Follow-Up Sequence

When they need a multi-email sequence (typically 4-6 emails).

  1. Start with the first email (Mode 1)
  2. Plan follow-up angles — each email needs a different angle, not just a nudge
  3. Set the gap cadence (Day 1, Day 4, Day 9, Day 16, Day 25)
  4. Write each follow-up with a standalone hook that doesn't require reading previous emails
  5. End with a breakup email that closes the loop professionally
  6. Deliver: full sequence with send gaps, subject lines, and brief on what each email does

Mode 3: Iterate from Performance Data

When they have an active sequence and want to improve it.

  1. Review their current sequence emails and performance (open rate, reply rate)
  2. Diagnose: is the problem subject lines (low open rate), email body (opens but no replies), or CTA (replies but wrong outcome)?
  3. Rewrite the underperforming element
  4. Deliver: revised emails + diagnosis + test recommendation

Core Writing Principles

1. Write Like a Peer, Not a Vendor

The moment your email sounds like marketing copy, it's over. Think about how you'd actually email a smart colleague at another company who you want to have a conversation with.

The test: Would a friend send this to another friend in business? If the answer is no — rewrite it.

  • ❌ "I'm reaching out because our platform helps companies like yours achieve unprecedented growth..."
  • ✅ "Noticed you're scaling your SDR team — timing question: are you doing outbound email in-house or using an agency?"

2. Every Sentence Earns Its Place

Cold email is the wrong place to be thorough. Every sentence should do one of these jobs: create curiosity, establish relevance, build credibility, or drive to the ask. If a sentence doesn't do one of those — cut it.

Read your draft aloud. The moment you hear yourself droning, stop and cut.

3. Personalization Must Connect to the Problem

Generic personalization is worse than none. "I saw you went to MIT" followed by a pitch has nothing to do with MIT. That's fake personalization.

Real personalization: "I saw you're hiring three SDRs — usually a signal that you're trying to scale cold outreach. That's exactly the challenge we help with."

The personalization must connect to the reason you're reaching out.

4. Lead With Their World, Not Yours

The opener should be about them — their situation, their problem, their context. Not about you or your product.

  • ❌ "We're a sales intelligence platform that..."
  • ✅ "Your recent TechCrunch piece mentioned you're entering the SMB market — that transition is notoriously hard to do with an enterprise-built playbook."

5. One Ask Per Email

Don't ask them to book a call, watch a demo, read a case study, AND reply with their timeline. Pick one ask. The more you ask for, the less likely any of it happens.


Voice Calibration by Audience

Adjust tone, length, and specificity based on who you're writing to:

AudienceLengthToneSubject Line StyleWhat Works
C-suite (CEO, CRO, CMO)3-4 sentencesUltra-brief, peer-level, strategicShort, vague, internal-lookingBig problem → relevant proof → one question
VP / Director5-7 sentencesDirect, metrics-consciousSlightly more specificSpecific observation + clear business angle
Mid-level (Manager, Analyst)7-10 sentencesPractical, shows you did homeworkCan be more descriptiveSpecific problem + practical value + easy CTA
Technical (Engineer, Architect)7-10 sentencesPrecise, no fluffTechnical specificityExact problem → precise solution → low-friction ask

The higher up the org chart, the shorter your email needs to be. A CEO gets 100+ emails per day. Three sentences and a clear question is a gift, not a slight.


Subject Lines: The Anti-Marketing Approach

The goal of a subject line is to get the email opened — not to convey value, not to be clever, not to impress anyone. Just open it.

The best cold email subject lines look like internal emails. They're short, slightly vague, and create just enough curiosity to click.

What Works

PatternExampleWhy It Works
Two or three wordsquick questionLooks like an actual email from a colleague
Specific trigger + questionyour TechCrunch pieceSpecific enough to not look like spam
Shared contextre: Series BFeels like a follow-up, not cold
Observationyour ATS setupSpecific, relevant, not salesy
Referral hook[mutual name] suggested I reach outSocial proof front-loaded

What Kills Opens

  • ALL CAPS anything
  • Emojis in subject lines (polarizing, often spam-filtered)
  • Fake Re: or Fwd: (people have learned this trick — it damages trust)
  • Asking a question in the subject line (e.g., "Are you struggling with X?") — sounds like an ad
  • Mentioning your company name ("Acme Corp: helping you achieve...")
  • Numbers that feel like blog headlines ("5 ways to improve your...")

Follow-Up Strategy

Most deals happen in follow-ups. Most follow-ups are useless. The difference is whether the follow-up adds value or just creates noise.

Cadence

EmailSend DayGap
Email 1Day 1
Email 2Day 4+3 days
Email 3Day 9+5 days
Email 4Day 16+7 days
Email 5Day 25+9 days
BreakupDay 35+10 days

Gaps increase over time. You're persistent but not annoying.

Follow-Up Rules

Each follow-up must have a new angle. Rotate through:

  • New piece of evidence (case study, data point, recent result)
  • New angle on the problem (a different pain point in their world)
  • Related insight (something you noticed about their industry, tech stack, or news)
  • Direct question (just ask plainly — sometimes clarity cuts through)
  • Reverse ask (ask for referral to the right person if you can't reach them)

Never "just check in." "Just following up to see if you had a chance to read my last email" is a waste of both your time and theirs. If you have nothing new to add, don't send the email.

Don't reference all previous emails. Each follow-up should stand alone. The prospect doesn't remember your earlier emails. Don't make them scroll.

The Breakup Email

The last email in a sequence should close the loop professionally. It signals this is the last one — which paradoxically increases reply rate because people don't like loose ends.

Example breakup:

"I'll stop cluttering your inbox after this one. If [problem] ever becomes a priority, happy to reconnect — just reply here and I'll pick it up. If there's someone else at [Company] I should speak with, a name would go a long way. Either way — good luck with [whatever's relevant]."

See references/follow-up-playbook.md for full cadence templates and angle rotation guide.


What to Avoid

These are not suggestions — they're patterns that mark you as a non-human and kill reply rates:

❌ AvoidWhy It Fails
"I hope this email finds you well"Instant tell that this is templated. Cut it.
"I wanted to reach out because..."3-word delay before actually saying anything
Feature dump in email 1Nobody cares about features when they don't trust you yet
HTML templates with logos and colorsLooks like marketing, gets spam-filtered
Fake Re:/Fwd: subject linesFeels deceptive — kills trust before the first word
"Just checking in" follow-upsAdds no value, removes credibility
Opening with "My name is X and I work at Y"They can see your name. Start with something interesting.
Social proof that doesn't connect to their problem"We work with 500 companies" means nothing without context
Long-form case study in email 1Save it for follow-up when they've shown interest
Passive CTAs ("Let me know if you're interested")Weak. Ask a direct question or propose a specific next step.

Deliverability Basics

A great email sent from a flagged domain never lands. Basics you need to have in place:

  • Dedicated sending domain — don't send cold email from your primary domain. Use mail.yourdomain.com or outreach.yourdomain.com.
  • SPF, DKIM, DMARC — all three must be configured and passing. Use mail-tester.com to verify.
  • Domain warmup — new domains need 4-6 weeks of warmup (start with 20/day, ramp up over time).
  • Plain text emails — or minimal HTML. Heavy HTML triggers spam filters.
  • Unsubscribe mechanism — required legally (CAN-SPAM, GDPR). Include a simple opt-out.
  • Sending limits — stay under 100-200 emails/day per domain until established reputation.
  • Bounce rate — above 5% hurts deliverability. Verify email lists before sending.

See references/deliverability-guide.md for domain warmup schedule, SPF/DKIM setup, and spam trigger word list.


Proactive Triggers

Surface these without being asked:

  • Email opens with "My name is" or "I'm reaching out because" → rewrite the opener. These are dead-on-arrival openers. Flag and offer an alternative that leads with their world.
  • First email is longer than 150 words → almost certainly too long. Flag word count and offer to trim.
  • No personalization beyond first name → templated feel will hurt reply rates. Ask if there's a trigger or signal they can work with.
  • Follow-up says "just checking in" or "circling back" → useless follow-up. Ask what new angle or value they can bring to that touchpoint.
  • HTML email template → recommend plain text. Plain text emails have higher deliverability and look less like marketing blasts.
  • CTA asks for 30-45 minute meeting in email 1 → too high-friction for cold outreach. Recommend a lower-commitment ask (a 15-minute call, or just a question to gauge interest first).

Output Artifacts

When you ask for...You get...
Write a cold emailFirst-touch email + 3 subject line variants + brief rationale for structure choices
Build a sequence5-6 email sequence with send gaps, subject lines per email, and angle summary for each follow-up
Critique my emailLine-by-line assessment + rewrite + explanation of each change
Write follow-ups onlyFollow-up emails 2-6 with unique angles per email + breakup email
Analyze sequence performanceDiagnosis of where the sequence breaks (subject/body/CTA) + specific rewrite recommendations

Communication

All output follows the structured communication standard:

  • Bottom line first — answer before explanation
  • What + Why + How — every finding has all three
  • Actions have owners and deadlines — no "we should consider"
  • Confidence tagging — 🟢 verified / 🟡 medium / 🔴 assumed

Related Skills

  • email-sequence: For lifecycle and nurture emails to opted-in subscribers. Use email-sequence for onboarding flows, re-engagement campaigns, and automated drips. NOT for cold outreach — that's cold-email.
  • copywriting: For marketing page copy. Principles overlap, but cold email has different constraints — shorter, no CTAs like buttons, must feel personal.
  • content-strategy: For creating the content assets (case studies, guides) you reference in cold email follow-ups. Good follow-up sequences often link to content.
  • marketing-strategy-pmm: For positioning and ICP definition. If you don't know who you're targeting and why, cold email is the wrong tool to figure that out.

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

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

04

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

补充不同宿主或平台的使用分布数据

能力 5

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

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

平台分布

OpenClaw

98.27%
按下载量换算3,352

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

只读

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

安装前确认

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

来源信息

继续浏览同类 Skills