vercel-labs/email-adaptation
Use when turning existing copy, a blog post, an announcement, or a brief into an email that works in an inbox, including deciding what to cut and what to link out to.
npx skills add https://github.com/vercel-labs/marketing-team-eve-template --skill email-adaptation
Someone hands you words that were written for a page and wants them sent as mail. The job is not to shorten them. It is to work out what the email is for, which is almost never the same as what the page was for.
A page answers a question someone already had. An email interrupts someone who did not ask. So the page can afford to build an argument, and the email has to earn the click to the page.
Attention is brief and it sits at the top. Nielsen Norman Group's 2006 eyetracking study found participants fully read 19% of the newsletters they opened, gave an opened one 51 seconds on average, and 67% of them recorded no eye fixations at all inside the newsletter's introduction, even though those introductions averaged about three lines. NN/g's 2010 round turns that into the rule to follow: lead with the content the reader values, because they rarely read far past it.
That same round also found readers arrive in different modes, some with a minute and some with ten, and advised committing to a brief mail or a leisurely one rather than a compromise that serves neither. That is the reason for the two shapes below.
Word count targets are the weakest part of the published advice. The figures in circulation disagree with each other, trace back to secondary citations rather than to studies, and the publishers printing them say scannability matters more than the count. So treat length as a consequence of what has to fit, not as a target to hit.
Before you cut a single sentence, answer three questions. If the brief does not settle them, ask rather than assuming.
Most adaptations are one of these. Pick deliberately, because mixing them produces an email that is too long to read and too thin to be useful.
The pointer. The email exists to get the click. Give the reader the single most interesting idea from the piece, enough context to know why it matters to them, and the link. Keep it short enough that the idea and the link are both there before any scrolling. This is the right shape for a blog post, a guide, or anything long: the piece is the destination, so do not reproduce it.
The whole thing. The email is the deliverable and there is nothing to click through to. An announcement, a short essay, a set of release notes, a personal note. It can run longer, but every paragraph still has to earn its place, and it still ends with one action.
The mistake to avoid is the third shape that happens by accident: two thirds of a blog post pasted into an email, ending in "read the rest". You have spent the reader's attention on the part you included and you are still asking them to leave to get the rest, so neither half of the mail is doing its job.
Cutting for email is not proportional trimming. Whole categories go.
What survives: the specific claim, the number or example that makes it concrete, the reason this reader should care, and the action.
Adaptation is not only subtraction. An email needs things a page does not.
email-style for how they work together.You are editing someone else's work, usually the content marketer's, and they made choices you cannot see from the copy alone.
references/patterns.md: worked shapes for the recurring email types, including the newsletter, the announcement, the nurture sequence, and the re-engagement mail, with what each one gets wrong most often.email-style carries the voice and the format limits, and writing-quality carries the word-level rules. This skill only covers the decisions about structure and scope.
Take vercel-labs/email-adaptation from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.