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-editinggit 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-editing)<a href="https://agentmods.dev/skills/vercel-labs/marketing-team-eve-template/content-editing"><img src="https://agentmods.dev/badge/skills/vercel-labs/marketing-team-eve-template/content-editing/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-editing"><img src="https://agentmods.dev/badge/skills/vercel-labs/marketing-team-eve-template/content-editing.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.00471 |
| Opus 5 | $0.00016 | $0.00235 |
| Sonnet 5 | $0.00006 | $0.00094 |
| Haiku 4.5 | $0.00003 | $0.00047 |
Grade A, and why
content-editing 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 editing
Edit in passes, one dimension at a time. Re-reading a draft looking for everything at once finds nothing; each pass below has a single question. After a pass, check you haven't broken an earlier one.
- Does it make sense? Find the sentences carrying two ideas, the pronouns with no clear referent, the jargon a reader outside the company wouldn't know, and the point buried under qualifications. Fix structure before wording.
- Does it sound like us? One voice throughout. Watch for the register slipping into corporate abstraction in the middle sections, which is usually where the writer got bored. Check against the brand context's voice, not your own defaults.
- Does the reader care? For each section, ask what the reader gets from it. A feature described without a consequence fails this pass: say what it lets them do or cut it. If the answer is "it's context", it's probably too long.
- Is it proven? Every claim needs a number, a source, a named example, or an explicit hedge. Mark the ones that have none. You are not verifying them here, you're finding them: flag what needs a source rather than softening it into vagueness.
- Is it specific? Replace the general with the concrete. "Significantly faster" becomes the measured figure; "many teams" becomes the count you can support; "leading companies" becomes names you have permission to use. If you can't get the specific, drop the claim rather than keeping the vague version.
Then the mechanical pass: cut hedges and filler, break up sentences over about 25 words, kill passive voice where an actor exists, make sure each paragraph opens on its own point, and check the opening earns the second sentence.
Read references/editing-checklist.md for the pass-by-pass checks, and references/common-problems.md for the recurring failure patterns and their fixes.
This skill is about structure and argument. writing-quality carries the word-level rules, the AI phrases to avoid, and the plain-English list; load both.
What ships with it
2 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 · 20 lines · 32 tokens per session scan A ac7bef675578
content-editing is a skill published in the GitHub repository vercel-labs/marketing-team-eve-template (436 stars, last pushed 22d ago), licensed MIT. It adds 32 tokens to every session and 471 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…