Use when drafting or editing a blog post or long-form article in the house voice.
npx skills add https://github.com/vercel-labs/eve-content-agent-template --skill blog-style
When writing or editing a blog post:
the words, so front-load the point — first in the post, first in each section and paragraph.
up any section that runs past ~300 words. Use lists for steps or anything parallel.
few hundred words; a real guide earns its length. Don't pad to hit a number.
hyphenated slug, 3–5 internal links with real anchor text, and alt text on meaningful images.
See references/format-specs.md for the numbers.
references/best-practices.md — sourced checklist of current blog tactics (scanning, hook,structure, readability, length, SEO basics, close).
references/format-specs.md — concrete specs: title/meta length, heading hierarchy, word-countranges, readability targets, slug, alt text, internal links.
references/banned-words.json — the list of words to avoid. Read it once up front forawareness, then run the lint_against_style tool on your draft to check it against this
file before proposing the draft to the writer.
Shared global references for all skills in the content agent. These apply regardless of the
content type.
references/ai-phrases-to-avoid.md — AI-tell words, phrases, and punctuation to avoid.references/plain-english-alternatives.md — plain-English swaps for bloated or vague wording.Take vercel-labs/eve-content-agent-template-blog-style from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.