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 positioninggit 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/positioning)<a href="https://agentmods.dev/skills/vercel-labs/marketing-team-eve-template/positioning"><img src="https://agentmods.dev/badge/skills/vercel-labs/marketing-team-eve-template/positioning/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/positioning"><img src="https://agentmods.dev/badge/skills/vercel-labs/marketing-team-eve-template/positioning.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.00041 | $0.00803 |
| Opus 5 | $0.00020 | $0.00402 |
| Sonnet 5 | $0.00008 | $0.00161 |
| Haiku 4.5 | $0.00004 | $0.00080 |
Grade A, and why
positioning 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 11d 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Positioning
Positioning is not a tagline. It's a decision about which market you're in and who you're beating, and the words come last. Work it in order, because each step constrains the next.
- What would this customer do if the product didn't exist? That's the real alternative, and it is often a spreadsheet, a contractor, an intern, or nothing at all rather than a competitor.
- What can you do that those alternatives can't? Only features that are actually hard to copy count here.
- What is the value that follows from those features, stated as something a customer gets rather than something the product has?
- Who cares most about that value? Not everyone who could use it: the segment that feels its absence most.
- What market does that put you in? The category the customer already searches, or a new one you have to teach.
Get 1, 2, and 4 right and the statement writes itself. Skip to the statement and you get something true of every product in the category.
Choosing the alternative you beat
The alternative determines everything downstream, and picking the wrong one is the most expensive error available. Positioning against a well-funded incumbent when your customers actually arrive from a spreadsheet means your messaging answers questions nobody is asking.
Ask the user directly what the last few customers used before, and take the most common answer over the most flattering one.
What counts as a differentiator
A differentiator survives three tests. It has to be true, provable, and hard to copy. Fail any one and it isn't yours to claim.
- True: the product actually does it today, not on the roadmap.
- Provable: you can point at a customer, a number, a demo, or a doc.
- Hard to copy: a competitor can't ship it next quarter. Being cheaper is rarely defensible; being architecturally different usually is.
Things that feel like differentiators and aren't: being easy to use, caring about customers, being fast, having a modern interface, being AI-powered. Every competitor claims all of these, so claiming them positions you nowhere. If a competitor's site would say the same sentence, delete 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.
- 11d ago First seen · 52 lines · 41 tokens per session scan A 67f4b880383c
positioning is a skill published in the GitHub repository vercel-labs/marketing-team-eve-template (435 stars, last pushed 22d ago), licensed MIT. It adds 41 tokens to every session and 803 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…