Writing Guidelines
- 35.1k installs
- 29.5k repo stars
- Updated July 24, 2026
- vercel-labs/agent-skills
writing-guidelines is an agent skill that Review docs/prose for Writing Guidelines compliance. Use when asked to "review my docs", "check writing style", "audit prose", "review docs voice and tone", or .
About
Review docs/prose for Writing Guidelines compliance. Use when asked to "review my docs", "check writing style", "audit prose", "review docs voice and tone", or "check this page against the writing handbook". --- name: writing-guidelines description: Review docs/prose for Writing Guidelines compliance. Use when asked to "review my docs", "check writing style", "audit prose", "review docs voice and tone", or "check this page against the writing handbook". metadata: author: vercel version: "1.0.0" argument-hint: <file-or-pattern> --- # Writing Guidelines Review files for compliance with Writing Guidelines. Fetch the latest guidelines from the source URL below 2. Read the specified files (or prompt user for files/pattern) 3. Check against all rules in the fetched guidelines 4. Output findings in the terse `file:line` format ## Guidelines Source Fetch fresh guidelines before each review: ``` https://raw.githubusercontent.com/vercel-labs/writing-guidelines/main/command.md ``` Use WebFetch to retrieve the latest rules.
- Fetch the latest guidelines from the source URL below
- Read the specified files (or prompt user for files/pattern)
- Check against all rules in the fetched guidelines
- Output findings in the terse `file:line` format
- Fetch guidelines from the source URL above
Writing Guidelines by the numbers
- 35,061 all-time installs (skills.sh)
- +4,256 installs in the week ending Jul 28, 2026 (Skillselion tracking)
- Ranked #13 of 2,184 Testing & QA skills by installs in the Skillselion catalog
- Data as of Jul 28, 2026 (Skillselion catalog sync)
writing-guidelines capabilities & compatibility
- Capabilities
- fetch the latest guidelines from the source url · read the specified files (or prompt user for fil · check against all rules in the fetched guideline · output findings in the terse `file:line` format · fetch guidelines from the source url above
- Use cases
- documentation
What writing-guidelines says it does
--- name: writing-guidelines description: Review docs/prose for Writing Guidelines compliance.
Use when asked to "review my docs", "check writing style", "audit prose", "review docs voice and tone", or "check this page against the writing handbook".
metadata: author: vercel version: "1.0.0" argument-hint: <file-or-pattern> --- # Writing Guidelines Review files for compliance with Writing Guidelines.
Fetch the latest guidelines from the source URL below 2.
npx skills add https://github.com/vercel-labs/agent-skills --skill writing-guidelinesAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 35.1k |
|---|---|
| repo stars | ★ 29.5k |
| Last updated | July 24, 2026 |
| Repository | vercel-labs/agent-skills ↗ |
What problem does writing-guidelines solve for developers using this skill?
Review docs/prose for Writing Guidelines compliance. Use when asked to "review my docs", "check writing style", "audit prose", "review docs voice and tone", or "check this page against the writing han
Who is it for?
Developers who need writing-guidelines patterns described in the cached skill documentation.
Skip if: Skip when docs are empty or the task is outside the skill's documented scope.
When should I use this skill?
Review docs/prose for Writing Guidelines compliance. Use when asked to "review my docs", "check writing style", "audit prose", "review docs voice and tone", or "check this page against the writing han
What you get
Actionable workflows and conventions from SKILL.md for writing-guidelines.
- file:line style audit report
By the numbers
- Metadata version 1.0.0
- Author metadata: vercel
Files
Writing Guidelines
Review files for compliance with Writing Guidelines.
How It Works
1. Fetch the latest guidelines from the source URL below 2. Read the specified files (or prompt user for files/pattern) 3. Check against all rules in the fetched guidelines 4. Output findings in the terse file:line format
Guidelines Source
Fetch fresh guidelines before each review:
https://raw.githubusercontent.com/vercel-labs/writing-guidelines/main/command.mdUse WebFetch to retrieve the latest rules. The fetched content contains all the rules and output format instructions.
Usage
When a user provides a file or pattern argument: 1. Fetch guidelines from the source URL above 2. Read the specified files 3. Apply all rules from the fetched guidelines 4. Output findings using the format specified in the guidelines
If no files specified, ask the user which files to review.
Related skills
TddFollow test-driven development with a strict red-green-refactor loop when creating reliable features or fixing bugs.510k185k
Test Driven DevelopmentEnforce writing failing tests before any production implementation code.176k260kQaRun conversational QA sessions that turn user-reported bugs into well-written, domain-aware GitHub issues without manual ticket writing.164k185kMigrate To ShoehornAutomatically update TypeScript test files that rely on unsafe `as` type assertions by replacing them with type-safe partial objects from @total-typescript/shoehorn.151k185k
Webapp TestingVerify frontend behavior, debug UI issues, capture screenshots, and inspect logs of a running local web application using Playwright.121k164k
Playwright CliRun browser automation, generate element snapshots, inspect DOM attributes, and execute Playwright tests from the terminal.96.3k12.2kForks & variants (2)
Writing Guidelines has 2 known copies in the catalog totaling 236 installs. They canonicalize to this original listing.
- millionco - 173 installs
- vercel-labs - 63 installs
How it compares
Pick writing-guidelines over generic grammar tools when the goal is Vercel handbook voice and tone, not spelling alone.
FAQ
What does writing-guidelines do?
Review docs/prose for Writing Guidelines compliance. Use when asked to "review my docs", "check writing style", "audit prose", "review docs voice and tone", or "check this page against the writing handbook".
When should I use writing-guidelines?
Review docs/prose for Writing Guidelines compliance. Use when asked to "review my docs", "check writing style", "audit prose", "review docs voice and tone", or "check this page against the writing handbook".
Is writing-guidelines safe to install?
Review the Security Audits panel on this page before installing in production.