JasonColapietro/suede-creator-skills / skills/suede-cold-email
suede-cold-email
VerifiedUse when asked "write a cold email" or to repair B2B outbound to qualified prospects. Suede produces sourced personalization, short subjects, bodies under 75 words, one ask and bounded follow-ups, with current sender-rule checks. NOT FOR: prospect qualification (use suede-prospecting), opted-in lifecycle email (use suede-emails), or broader sales collateral (use suede-sales-enablement).
| File | Kind | Size |
|---|---|---|
| CARD.md | markdown | 4.4 KB |
| SKILL.md | skill md | 9.9 KB |
| agents/openai.yaml | config | 558 B |
| evals/evals.json | config | 6.9 KB |
| references/benchmarks.md | markdown | 6.1 KB |
| references/follow-up-sequences.md | markdown | 2.6 KB |
| references/frameworks.md | markdown | 3.8 KB |
| references/personalization.md | markdown | 3.0 KB |
| references/subject-lines.md | markdown | 1.8 KB |
| references/usage-contract.md | markdown | 889 B |
references/personalization.md
View on GitHub# Personalization
Personalization earns a reply only when it connects to the problem you solve.
An observation that leads nowhere is an attention hack, and readers spot it.
## Four depths
| Depth | What it uses | Effort | When it is enough |
|---|---|---|---|
| 1. Merge fields | Name, company, title | None | Never on its own; table stakes |
| 2. Segment | Industry pains, regulation, seasonality | Low, scales | High-volume campaigns to a tight segment |
| 3. Role | What this role owns and worries about | Low, scales | Mid-level buyers with a common job |
| 4. Individual | A specific, recent, verifiable fact about this person or company | High | Top accounts and senior buyers |
Examples:
- Segment: "Most dental groups adding a second location hit a scheduling
bottleneck before they hit a staffing one."
- Role: "As head of sales with a two-person RevOps team, you're probably
building the forecast yourself."
- Individual: "Noticed you're hiring three SDRs. Teams usually hit follow-up
fatigue during that ramp."
## Signal sources
| Signal | Where it comes from | How it opens an email |
|---|---|---|
| Funding | Press release, company blog, public filings | Scaling pressure the round creates |
| Hiring | Careers page, job boards | The work the new hires will run into |
| Tech stack | The company's own site, public integration listings | A known ceiling of the tool they use |
| Posts and talks | Their public posts, podcast appearances, conference talks | One specific point they made, tied to your problem |
| Company news | Press, product changelog | The challenge the change usually creates |
| Site changes | A direct look at their pricing, docs, or onboarding | A specific observation, framed as a question |
Every signal must go in the `Personalization source:` field of the output so the
user can confirm it is real. No source, no personalization.
## A fast repeatable system
1. List the ten buying signals that matter most for this product, plus five
company triggers and five person triggers. Rank them.
2. Write one short bridge paragraph per trigger that moves from the signal to
the problem.
3. Keep the problem, proof, and ask constant. Swap only the opening.
With the bridges written, a researched first touch takes a few minutes.
## Four lenses on the buyer
- **Demographic:** role, seniority, background.
- **Technographic:** the tools they run.
- **Firmographic:** size, stage, funding, industry, growth.
- **Psychographic:** what they care about and argue for in public. Highest
impact and the hardest to fake, so use it only with a real source.
## What reads as fake
- "I hope this email finds you well" and other machine openers.
- A compliment unrelated to the pitch ("Cool that you went to UCLA!").
- "I came across your profile and wanted to reach out."
- Detail so personal it feels like surveillance.
## The "so what?" test
Read the opening line as the prospect. If the honest reaction is "so what?",
rewrite it until the line points at a problem they would admit to having.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |