Agent skill · Documentation

suede-cold-email

Suede-owned B2B cold-email discipline for evidence-based personalization, subject lines, opening lines, concise bodies, one clear CTA, and bounded follow-up sequences. Use when writing or repairing outbound email to qualified prospects. NOT FOR: building or qualifying the prospect list (use suede-prospecting), lifecycle or nurture email (use suede-emails), or broader sales collateral (use suede-sales-enablement).

JasonColapietrogithub.com/JasonColapietroGitHub ↗
claude-codecodexMIT
Install
npx skills add JasonColapietro/suede-creator-skills --skill suede-cold-email --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 8
SKILL.md size: 7 KB
Bundled scripts: none
Version: 2.0.0
Path: skills/suede-cold-email/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 165
Language: JavaScript

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Suede Cold Email Writing Use this Suede cold-email playbook to write concise, evidence-grounded outreach that sounds human and respects the recipient. ## 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 em

What's inside
Steps it walks through
  1. Before Writing
  2. Writing Principles
  3. Write like a peer, not a vendor
  4. Every sentence must earn its place
  5. Personalization must connect to the problem
  6. Lead with their world, not yours
  7. One ask, low friction
  8. Voice & Tone
  9. Structure
  10. Subject Lines
  11. Follow-Up Sequences
  12. Quality Check
  13. What to Avoid
  14. Data & Benchmarks
Ships with 7 files
  • agents/openai.yaml
  • evals/evals.json
  • references/benchmarks.md
  • references/follow-up-sequences.md
  • references/frameworks.md
  • references/personalization.md
  • references/subject-lines.md
More from suede-creator-skills
All skills →
About this skill
What does the suede-cold-email skill do?

Suede-owned B2B cold-email discipline for evidence-based personalization, subject lines, opening lines, concise bodies, one clear CTA, and bounded follow-up sequences. Use when writing or repairing outbound email to qualified prospects. NOT FOR: building or qualifying the prospect list (use suede-prospecting), lifecycle or nurture email (use suede-emails), or broader sales collateral (use suede-sales-enablement).

How do I install it?

Run `npx skills add JasonColapietro/suede-creator-skills --skill suede-cold-email --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From JasonColapietro/suede-creator-skills, a repository with 165 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going