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 resend-buildgit 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/resend-build)<a href="https://agentmods.dev/skills/vercel-labs/marketing-team-eve-template/resend-build"><img src="https://agentmods.dev/badge/skills/vercel-labs/marketing-team-eve-template/resend-build/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/resend-build"><img src="https://agentmods.dev/badge/skills/vercel-labs/marketing-team-eve-template/resend-build.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.00032 | $0.01086 |
| Opus 5 | $0.00016 | $0.00543 |
| Sonnet 5 | $0.00006 | $0.00217 |
| Haiku 4.5 | $0.00003 | $0.00109 |
Grade A, and why
resend-build 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Building in Resend
The tools are discoverable but the order matters, and several of them fail in ways that are quiet rather than loud. Read this before the first call, not after a call goes wrong.
Resend's tools are not preloaded. Find them with connection_search, then call them by their qualified name. Don't guess at a tool name or its arguments.
The build order
For a broadcast, which is one email to a segment:
list-domainsand pick a verified one for the from address.list-segmentsand pick the target. A broadcast requires a segment: there is no send-to-everyone option. If nothing covers the intended audience, say so and agree a segment with the user before creating one.create-broadcastwith the name, segment, subject, and the plain text version. This does not send.get-tiptap-json-contentwithinclude_schema: true, thencompose-broadcastto set the body.- Show the user what you built: subject, preview text, from, segment and its size, and the send time.
send-broadcast, which pauses for approval.
For a template, which is a reusable email with variables:
create-template. It is created as a draft.get-tiptap-json-contentwithinclude_schema: true, thencompose-template.publish-template. A template cannot be used for sending until it is published, and re-publishing is how an edit goes live.
The traps
Always read before you compose. Call get-tiptap-json-content before compose-broadcast or compose-template, even when you are certain the body is empty. Someone may have edited it in the dashboard, and composing without reading overwrites their work.
Two content modes, and switching loses work. Content set with compose-* is editable in the Resend visual editor; content set with update-broadcast's html and text fields is not. Moving between the two modes is lossy. Prefer compose-* so the user can refine it themselves, and if raw HTML is genuinely wanted, ask before switching an existing body over.
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 · 57 lines · 32 tokens per session scan A 602f2acc2c81
resend-build is a skill published in the GitHub repository vercel-labs/marketing-team-eve-template (436 stars, last pushed 23d ago), licensed MIT. It adds 32 tokens to every session and 1,086 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…