vercel-labs/marketing-team-eve-template is a deployable team of AI marketing agents led by a coordinating agent that delegates launches, writing, and conversion work to specialists. Teams use it through Slack or a terminal to create blog drafts, social posts, and email campaigns in Notion, Typefully, and Resend, with approval required for irreversible actions. The catalogue skills and instructions define workflows for using this marketing team.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add vercel-labs/marketing-team-eve-template --skill email-adaptationgit clone --depth 1 https://github.com/vercel-labs/marketing-team-eve-templateWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/vercel-labs/marketing-team-eve-template/email-adaptation)<a href="https://agentmods.dev/skills/vercel-labs/marketing-team-eve-template/email-adaptation"><img src="https://agentmods.dev/badge/skills/vercel-labs/marketing-team-eve-template/email-adaptation/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/vercel-labs/marketing-team-eve-template/email-adaptation"><img src="https://agentmods.dev/badge/skills/vercel-labs/marketing-team-eve-template/email-adaptation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00037 | $0.01857 |
| Opus 5 | $0.00018 | $0.00928 |
| Sonnet 5 | $0.00007 | $0.00371 |
| Haiku 4.5 | $0.00004 | $0.00186 |
Grade A, and why
email-adaptation scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 13d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Adapting copy into an email
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.
How email gets read
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.
Decide the email's job first
Before you cut a single sentence, answer three questions. If the brief does not settle them, ask rather than assuming.
- What is the one action you want? Read the post, book the call, reply, upgrade, show up. One, not three. A mail that asks for three things has not decided what it is for, and it makes the reader do that work in the seconds they have given you.
- What does this reader already know? A list of existing customers and a list of cold signups need different first lines, and the same email cannot serve both.
- What happens if they do nothing? If the honest answer is nothing, this may not need to be an email, and saying so is more useful than sending it.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 13d ago First seen · 82 lines · 37 tokens per session scan A 07bd64800e8f
email-adaptation is a skill published in the GitHub repository vercel-labs/marketing-team-eve-template (436 stars, last pushed 23d ago), licensed MIT. It adds 37 tokens to every session and 1,857 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
writing-quality
Writing-quality guardrails for any prose the agent drafts or edits: blog posts, page copy, Notion drafts, release notes, marketing text. Use this skill whenever writing or revising content meant for humans to read, to keep the prose natural, plain, and free of AI-sounding phrasing. Not needed for code, queries, or…
sanity-best-practices
Sanity development best practices for schema design, GROQ queries, TypeGen, Visual Editing, images, Portable Text, Studio structure, localization, migrations, Sanity Functions, Blueprints, and framework integrations such as Next.js, Nuxt, Astro, Remix, SvelteKit, Angular, Hydrogen, and the App SDK. Use this skill…
portable-text-serialization
Render and serialize Portable Text to React, Svelte, Vue, Astro, HTML, Markdown, and plain text. Use when implementing Portable Text rendering in any frontend framework, building custom serializers for non-standard block types, converting Portable Text to HTML strings server-side, converting Portable Text to Markdown…
portable-text-conversion
Convert HTML and Markdown content into Portable Text blocks for Sanity. Use when migrating content from legacy CMSs, importing HTML or Markdown into Sanity, building content pipelines that ingest external content, converting rich text between formats, or programmatically creating Portable Text documents. Covers…
seo-aeo-best-practices
SEO and AEO best practices for metadata, Open Graph, sitemaps, robots.txt, hreflang, JSON-LD structured data, EEAT, and content optimized for search engines and AI answer surfaces. Use this skill when implementing page SEO, technical SEO, schema markup, international SEO, AI-overview readiness, or improving content…
content-experimentation-best-practices
Content experimentation and A/B testing guidance covering experiment design, hypotheses, metrics, sample size, statistical foundations, CMS-managed variants, and common analysis pitfalls. Use this skill when planning experiments, setting up variants, choosing success metrics, interpreting statistical results, or…