Writing GuidelinesSkill

Writing Guidelines is an official agent skill from Vercel that applies the company's internal writing handbook to your documentation the same way a linter applies rules to code.

Point it at a docs page, a README or a changelog entry — "review my docs", "check writing style", "audit prose" — and it fetches the current ruleset from the vercel-labs/writing-guidelines repository, reads the files you name, and returns violations as terse file:line findings.

What it checks. The handbook covers voice and tone, document structure and heading hierarchy, the conventions that differ by content type (a tutorial is not a reference page is not a release note), how code samples should be written and introduced, typography and punctuation, and guidance for prose that will be read by AI agents as well as by people.

Why a skill rather than a style guide in a wiki. A style guide only works if someone remembers to apply it. As a skill it runs on demand against the actual file, catches the drift that accumulates when a dozen people write docs, and gives a reviewer something concrete to point at instead of "this doesn't sound like our docs".

Who it is for. Developer-experience and documentation teams, open-source maintainers who want consistent READMEs across repositories, and engineers who write docs but would rather not memorise a handbook to do it.

Like the rest of the collection the ruleset is fetched fresh on each run rather than vendored, so reviews track upstream automatically. MIT-licensed, part of vercel-labs/agent-skills, installable with npx skills add vercel-labs/agent-skills, and compatible with any agent that reads SKILL.md.