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 content-planninggit 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/content-planning)<a href="https://agentmods.dev/skills/vercel-labs/marketing-team-eve-template/content-planning"><img src="https://agentmods.dev/badge/skills/vercel-labs/marketing-team-eve-template/content-planning/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/content-planning"><img src="https://agentmods.dev/badge/skills/vercel-labs/marketing-team-eve-template/content-planning.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.00030 | $0.00427 |
| Opus 5 | $0.00015 | $0.00214 |
| Sonnet 5 | $0.00006 | $0.00085 |
| Haiku 4.5 | $0.00003 | $0.00043 |
Grade A, and why
content-planning 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 12d 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.
What it actually says
Content planning
When deciding what to write, before writing it:
- Start from why someone buys, not from a keyword list. A topic earns a place if it either answers a question a buyer actually has or shows the product doing the thing they're stuck on. Volume without either is traffic that never converts.
- Know which kind of piece you're writing. Searchable content answers a query someone typed and lives or dies on being findable: it needs the question in the title, a direct answer near the top, and durable structure. Shareable content earns attention on its own: an opinion, original data, a story with a specific outcome. Optimizing one as though it were the other produces a piece that does neither.
- Match the piece to where the reader is:
- Unaware of the problem: symptoms, not solutions. Name the thing they're experiencing.
- Comparing approaches: how the options actually differ, including where yours is the wrong choice.
- Comparing products: specifics. Pricing, migration, limits, what breaks.
- Already sold: implementation, onboarding, getting to value.
- Group topics rather than listing them. Pick a few pillars the team wants to be known for, then write clusters of related pieces under each that link to one another. Ten pieces on three pillars beats thirty scattered ones, because the cluster compounds and the scatter doesn't.
- Check a topic isn't already covered before adding it. Two pieces answering the same question split the traffic and neither wins; strengthening the existing piece usually beats writing a second.
- Prioritize honestly. The best next piece is the one with real demand, a clear tie to the product, and evidence you can actually get. When you're missing the evidence, either go find it or pick a different topic.
Read references/buyer-stage-topics.md for questions to mine at each stage and where to find them.
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.
- 12d ago First seen · 21 lines · 30 tokens per session scan A 7a92ca1f6658
content-planning is a skill published in the GitHub repository vercel-labs/marketing-team-eve-template (436 stars, last pushed 23d ago), licensed MIT. It adds 30 tokens to every session and 427 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…