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/frameworks.md
View on GitHub# Cold Email Shapes
A shape is a thinking pattern, not a template. Pick the one that fits the
evidence you actually have, then write in plain words. Every example below uses
placeholder companies and numbers; replace them with real, checkable proof or
cut the proof sentence.
## Choosing a shape
| You have... | Use |
|---|---|
| A strong trigger event (funding, hiring, launch, new exec) | Trigger Note |
| A clear observation about their situation | Observation Question |
| A problem-aware reader who has not shopped yet | Problem First |
| A customer story from a similar company | Peer Story |
| A senior reader and very little time | Two-Line Note |
| An analytical reader (engineering, finance, ops) | Claim and Proof |
| A clean before and after | Before, After, Bridge |
## Problem First (the default)
Name the pain, show what it costs, offer the fix, ask softly.
> Most sales leaders at your stage lose a day a week to manual CRM reports,
> and the forecast that reaches the board is a week stale by the time it lands.
> We generate those reports live from the CRM. [Customer] cut reporting time
> by [verified %]. Worth seeing how?
## Observation Question
One observation, one yes-or-no value question. Two sentences.
> Looks like you're hiring three SDRs. Would a weekly read on how each one is
> ramping on email be useful?
## Trigger Note
Trigger, the challenge it usually creates, a hint at the fix, a binary ask. No
intro, no company description. One to three sentences.
> Congrats on the Series B. Doubling the sales team usually breaks onboarding
> first. We shorten ramp for new reps. Open to a look?
## Before, After, Bridge
The current painful state, the better state, your product as the path.
> Right now your team is sourcing leads by hand, and pipeline swings every
> quarter. The better version is qualified leads arriving daily and reps
> selling all day. That's the gap we close. [Customer] saw [verified result].
> Want the short version?
## Peer Story
A customer as the main character, their problem, what changed.
> Last year the VP Sales at a Series B company had five SDRs up against a
> competitor with twenty. They moved prospect research into our tool and
> tripled personalized volume without losing quality. In 90 days they booked
> more meetings than the bigger team. Happy to share how it could work for
> [Company].
Use only stories the user can verify and is allowed to share.
## Situation, Complication, Question
Mirrors how operators brief leadership. Good for consultative sales.
> Your team doubled this year. That usually means onboarding is eating into
> selling time. How are you handling ramp for new hires?
## Claim and Proof
A contrarian claim, a plain explanation, a proof point, a clear ask.
> Most sales teams measure rep activity. The best ones measure rep efficiency.
> When [Customer] switched, they booked [verified %] more meetings with fewer
> emails. Worth seeing the scorecard?
## Two-Line Note
For executives. Context in one line, the question in the next.
> Saw the expansion into Austin. Is staffing the second site on your plate
> this quarter?
## Compliment, Case, Ask (services and agencies)
A specific, earned compliment, a relevant piece of work, an ask.
> The new pricing page is sharp, especially the usage calculator. We just
> rebuilt onboarding for [comparable company] and have two ideas for yours.
> Interested?
## Five-Part Base
When nothing above fits: observation, problem or insight, credibility, the
fix, an invitation to talk. Keep each part to one sentence.
## Multi-touch arc
For a sequence, spread one argument across touches instead of repeating it:
problem, then why it matters more than they think, then a short story, then
proof, then the offer, then a final low-pressure ask. Each touch must stand
alone. See [follow-up-sequences.md](follow-up-sequences.md).
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 |