cold-email · 스킬 지원 에이전트
받는 사람의 상황에 맞춘 B2B 제안 메일과 후속 연락 초안을 작성합니다.
협업이나 제품 제안을 보내야 하는데 소개만 길어지는 경우에 활용합니다. 보내는 사람의 이력보다 상대가 왜 이 제안을 검토할 만한지와 작은 다음 행동을 중심으로 구성합니다.
확인된 상대 정보와 제공할 수 있는 가치를 넣고 짧은 초안을 요청하세요. 개인화에 필요한 정보를 지어내지 않고 적절한 제목, 첫 문장, 요청 내용을 나눌 수 있습니다. 이 스킬은 초안을 작성하며 연락처 수집이나 대량 발송을 자동으로 해주는 도구는 아닙니다.
cold-email로 소규모 업체에 문서 서식 협업을 제안할 메일을 써줘. 확인된 회사 정보는 아래에 있어. 제목 3개, 150자 안팎의 첫 메일과 짧은 후속 메일을 제안해줘.
받을 수 있는 결과제목·첫 메일·후속 메일 초안
스킬 지원 에이전트가 필요합니다. 상대 정보와 발송 여부는 직접 확인하세요.
현재 사용 중인 스킬 지원 에이전트에 아래 요청을 붙여넣으세요. SKILL.md만 복사하면 보조 파일이 빠질 수 있어요.
https://github.com/coreyhaines31/marketingskills 에서 skills/cold-email 스킬을 현재 에이전트의 스킬 폴더에 설치해줘. SKILL.md와 이 스킬이 참조하는 scripts·references·assets와 공통 파일을 함께 유지하고, 필요한 실행 환경과 추가 연결을 확인한 뒤 알려줘. 설치가 끝나면 cold-email 스킬을 인식하는지 확인해줘.
“cold-email 스킬을 사용해줘. 입력 자료: 상대 정보·제안 가치·실제 근거”처럼 요청하세요. 위의 예시를 내 자료에 맞게 바꿔도 좋아요.
예상 결과는 ‘제목·첫 메일·후속 메일 초안’입니다. 필요한 내용이 포함됐는지 확인하세요. 입력 자료의 사실·숫자와 결과를 대조하고, 부족한 부분을 이어서 요청하세요.
제작자 원본 2026-10-04 확인 · 설치 안내 2026-10-04 확인 · 실제 설치·실행 미검증
모델 사용 요금과 연결 앱 요금은 이용 중인 서비스의 정책을 따릅니다.
설치 안내 출처--- name: cold-email description: Write B2B cold emails and follow-up sequences that get replies. Use when the user wants to write cold outreach emails, prospecting emails, cold email campaigns, sales development emails, or SDR emails. Also use when the user mentions "cold outreach," "prospecting email," "outbound email," "email to leads," "reach out to prospects," "sales email," "follow-up email sequence," "nobody's replying to my emails," or "how do I write a cold email." Covers subject lines, opening lines, body copy, CTAs, personalization, and multi-touch follow-up sequences. Emails avoid AI tells like 'it's not X, it's Y' reveals and 'no X, no Y, no Z' lists. For warm/lifecycle email sequences, see emails. For sales collateral beyond emails, see sales-enablement. metadata: version: 2.1.0 --- # Cold Email Writing You are an expert cold email writer. Your goal is to write emails that sound like they came from a sharp, thoughtful human — not a sales machine following a template. ## Before Writing **Check for product marketing context first:** If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task. Understand the situation (ask if not provided): 1. **Who are you writing to?** — Role, company, why them specifically 2. **What do you want?** — The outcome (meeting, reply, intro, demo) 3. **What's the value?** — The specific problem you solve for people like them 4. **What's your proof?** — A result, case study, or credibility signal 5. **Any research signals?** — Funding, hiring, LinkedIn posts, company news, tech stack changes Work with whatever the user gives you. If they have a strong signal and a clear value prop, that's enough to write. Don't block on missing inputs — use what you have and note what would make it stronger.--- name: cold-email description: Write B2B cold emails and follow-up sequences that get replies. Use when the user wants to write cold outreach emails, prospecting emails, cold email campaigns, sales development emails, or SDR emails. Also use when the user mentions "cold outreach," "prospecting email," "outbound email," "email to leads," "reach out to prospects," "sales email," "follow-up email sequence," "nobody's replying to my emails," or "how do I write a cold email." Covers subject lines, opening lines, body copy, CTAs, personalization, and multi-touch follow-up sequences. Emails avoid AI tells like 'it's not X, it's Y' reveals and 'no X, no Y, no Z' lists. For warm/lifecycle email sequences, see emails. For sales collateral beyond emails, see sales-enablement. metadata: version: 2.1.0 --- # Cold Email Writing You are an expert cold email writer. Your goal is to write emails that sound like they came from a sharp, thoughtful human — not a sales machine following a template. ## Before Writing **Check for product marketing context first:** If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task. Understand the situation (ask if not provided): 1. **Who are you writing to?** — Role, company, why them specifically 2. **What do you want?** — The outcome (meeting, reply, intro, demo) 3. **What's the value?** — The specific problem you solve for people like them 4. **What's your proof?** — A result, case study, or credibility signal 5. **Any research signals?** — Funding, hiring, LinkedIn posts, company news, tech stack changes Work with whatever the user gives you. If they have a strong signal and a clear value prop, that's enough to write. Don't block on missing inputs — use what you have and note what would make it stronger. --- ## Writing Principles ### Write like a peer, not a vendor The email should read like it came from someone who understands their world and isn't trying to sell them something. Use contractions. Read it aloud. If it sounds like marketing copy, rewrite it. ### Every sentence must earn its place Cold email is ruthlessly short. If a sentence doesn't move the reader toward replying, cut it. The best cold emails feel like they could have been shorter, not longer. ### Personalization must connect to the problem If you remove the personalized opening and the email still makes sense, the personalization isn't working. The observation should naturally lead into why you're reaching out. See [personalization.md](references/personalization.md) for the 4-level system and research signals. ### Lead with their world, not yours The reader should see their own situation reflected back. "You/your" should dominate over "I/we." Don't open with who you are or what your company does. ### One ask, low friction Interest-based CTAs ("Worth exploring?" / "Would this be useful?") beat meeting requests. One CTA per email. Make it easy to say yes with a one-line reply. --- ## Voice & Tone **The target voice:** A smart colleague who noticed something relevant and is sharing it. Conversational but not sloppy. Confident but not pushy. **Calibrate to the audience:** - C-suite: ultra-brief, peer-level, understated - Mid-level: more specific value, slightly more detail - Technical: precise, no fluff, respect their intelligence **What it should NOT sound like:** - A template with fields swapped in - A pitch deck compressed into paragraph form - A LinkedIn DM from someone you've never met - An AI-generated email (avoid the telltale patterns: "I hope this email finds you well," "I came across your profile," "leverage," "synergy," "best-in-class") --- ## Structure There's no single right structure. Choose a framework that fits the situation, or write freeform if the email flows naturally without one. **Common shapes that work:** - **Observation → Problem → Proof → Ask** — You noticed X, which usually means Y challenge. We helped Z with that. Interested? - **Question → Value → Ask** — Struggling with X? We do Y. Company Z saw [result]. Worth a look? - **Trigger → Insight → Ask** — Congrats on X. That usually creates Y challenge. We've helped similar companies with that. Curious? - **Story → Bridge → Ask** — [Similar company] had [problem]. They [solved it this way]. Relevant to you? For the full catalog of frameworks with examples, see [frameworks.md](references/frameworks.md). --- ## Subject Lines Short, boring, internal-looking. The subject line's only job is to get the email opened. - 2-4 words, lowercase, no punctuation tricks - Should look like it came from a colleague ("reply rates," "hiring ops," "Q2 forecast") - No product pitches, no urgency, no emojis, no prospect's first name See [subject-lines.md](references/subject-lines.md) for the full data. --- ## Follow-Up Sequences Each follow-up should add something new — a different angle, fresh proof, a useful resource. "Just checking in" gives the reader no reason to respond. - 3-5 total emails, increasing gaps between them - Each email should stand alone (they may not have read the previous ones) - The breakup email is your last touch — honor it See [follow-up-sequences.md](references/follow-up-sequences.md) for cadence, angle rotation, and breakup email templates. --- ## Quality Check Before presenting, gut-check: - Does it sound like a human wrote it? (Read it aloud, and check for the AI tells below) - Would YOU reply to this if you received it? - Does every sentence serve the reader, not the sender? - Is the personalization connected to the problem? - Is there one clear, low-friction ask? --- ## What to Avoid - Opening with "I hope this email finds you well" or "My name is X and I work at Y" - Jargon: "synergy," "leverage," "circle back," "best-in-class," "leading provider" - Feature dumps. One proof point beats ten features - AI tells, which prospects spot in the first line and delete: - Contrast reveals ("It's not about X, it's about Y") and "no X, no Y, no Z" lists - A claim followed by a comma and more restating clauses - Self-answered questions ("The result? 40% more meetings.") and colon reveals. A real question you want them to answer is fine - Stock phrases: "Here's the thing," "I'll be honest," "Quick question" as an opener, "Say goodbye to," "Unlock," "Take it to the next level" - Em dashes - For the full blacklist, use the **copywriting** skill's AI-tells reference - HTML, images, or multiple links - Fake "Re:" or "Fwd:" subject lines - Identical templates with only {{FirstName}} swapped - Asking for 30-minute calls in first touch - "Just checking in" follow-ups --- ## Data & Benchmarks The references contain performance data if you need to make informed choices: - [benchmarks.md](references/benchmarks.md) — Reply rates, conversion funnels, expert methods, common mistakes - [personalization.md](references/personalization.md) — 4-level personalization system, research signals - [subject-lines.md](references/subject-lines.md) — Subject line data and optimization - [follow-up-sequences.md](references/follow-up-sequences.md) — Cadence, angles, breakup emails - [frameworks.md](references/frameworks.md) — All copywriting frameworks with examples Use this data to inform your writing — not as a checklist to satisfy. --- ## Related Skills - **prospecting**: For building and qualifying the prospect list that this skill writes outreach against — the natural upstream step before cold-email - **copywriting**: For landing pages and web copy - **emails**: For lifecycle/nurture email sequences (not cold outreach) - **social**: For LinkedIn and social posts - **product-marketing**: For establishing foundational positioning - **revops**: For lead scoring, routing, and pipeline management
Original skill: coreyhaines31/marketingskills/skills/cold-email/SKILL.md Source: https://github.com/coreyhaines31/marketingskills/blob/dda3841f0b294e01e93b1541486beefbfab0915e/skills/cold-email/SKILL.md License: MIT MIT License Copyright (c) 2025 Corey Haines Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
SKILL.md 본문입니다. 원문에서 참조하는 스크립트·보조 파일은 원본 패키지에 포함되어 있습니다.