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 blog-stylegit 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/blog-style)<a href="https://agentmods.dev/skills/vercel-labs/marketing-team-eve-template/blog-style"><img src="https://agentmods.dev/badge/skills/vercel-labs/marketing-team-eve-template/blog-style/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/blog-style"><img src="https://agentmods.dev/badge/skills/vercel-labs/marketing-team-eve-template/blog-style.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.00017 | $0.00525 |
| Opus 5 | $0.00009 | $0.00262 |
| Sonnet 5 | $0.00003 | $0.00105 |
| Haiku 4.5 | $0.00002 | $0.00052 |
Grade A, and why
blog-style 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.
How it starts
The opening of the file, as written. The whole thing — 34 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Blog voice & style
When writing or editing a blog post:
- Lead with the reader's problem, not the product. Most people scan and read maybe a quarter of the words, so front-load the point: first in the post, first in each section and paragraph.
- Short paragraphs, 2–4 sentences, one idea each. White space is a feature, not filler.
- Descriptive subheads that read as a map: skim only the H2s and you should get the gist. Break up any section that runs past ~300 words. Use lists for steps or anything parallel.
- Most sentences under ~20 words. Active voice. Cut hedges: "just", "simply", "very", "really".
- Concrete over abstract; show an example before stating a principle.
- No exclamation points; no "in today's fast-paced world" openers.
- Match length to what the question needs; there's no magic word count. A quick answer can be a few hundred words; a real guide earns its length. Don't pad to hit a number.
- Mind the SEO surface: one descriptive title (~50–60 chars, keyword near the front), a short hyphenated slug, 3–5 internal links with real anchor text, and alt text on meaningful images. See
references/format-specs.mdfor the numbers.
Structure
- Hook: the problem or tension, in the reader's words; promise the payoff and preview it.
- Stakes: why it matters now.
- Payoff: the idea/solution, with one concrete example.
- Close: the single takeaway, then one focused next step. No "in conclusion".
References
references/best-practices.md: sourced checklist of current blog tactics (scanning, hook, structure, readability, length, SEO basics, close).references/format-specs.md: concrete specs for title and meta length, heading hierarchy, word-count ranges, readability targets, slug, alt text, and internal links.references/banned-words.json: the words to avoid. Thelint_against_styletool checks a draft against this list, so run the tool rather than reading the file.
Layers on top of
The writing-quality skill carries the surface-independent rules: AI tells, plain-English swaps, front-loading, concrete over abstract, voice. Load it too; this skill only adds what's specific to blog posts.
What ships with it
3 files 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 · 34 lines · 17 tokens per session scan A 6303cf255539
blog-style is a skill published in the GitHub repository vercel-labs/marketing-team-eve-template (436 stars, last pushed 23d ago), licensed MIT. It adds 17 tokens to every session and 525 once invoked, about $0.0001 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…