writing-guidelines

Review documentation and prose files against Vercel's Writing Guidelines rules.

Updated Aug 22, 2026
One-click install
npx skills add https://github.com/MSC72m/DevForge --skill writing-guidelines-msc72m
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-guidelines
Source: https://github.com/MSC72m/DevForge/tree/main/skills/writing-guidelines
Command: npx skills add https://github.com/MSC72m/DevForge --skill writing-guidelines-msc72m

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping documentation and prose consistent with a style guide is tedious and error-prone when done manually. This Skill automates compliance reviews by fetching the latest Writing Guidelines and checking your files against every rule. ## Core Features & Use Cases - Fresh Rule Fetching: Retrieves the latest guidelines from the vercel-labs/writing-guidelines repository before each review, so checks always reflect current rules. - File and Pattern Review: Accepts a file path or glob pattern argument to review one or many documents in a single pass. - Terse Findings Output: Reports violations in a compact file:line format for quick navigation and fixing. - Use Case: Before publishing a docs update, run the review across all changed Markdown pages to catch voice, tone, and style violations before they reach readers. ## Quick Start Ask the assistant to review docs/intro.md against the writing guidelines and list all violations.

Frequently Asked Questions about writing-guidelines

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review my docs against writing style guidelines?▼

Provide a file path or glob pattern as the argument, and the Skill fetches the latest Writing Guidelines, reads your files, and checks them against every rule. Findings are reported in a terse file:line format.

What writing guidelines does this Skill check against?▼

It fetches the rules from the vercel-labs/writing-guidelines repository's command.md file on GitHub. The guidelines are retrieved fresh before each review, so checks always use the current version.

Can I review multiple documentation files at once?▼

Yes, you can pass a file pattern instead of a single file to review many documents in one run. If you provide no argument, the Skill asks which files you want reviewed.

Does the writing guidelines review require internet access?▼

Yes, the Skill uses WebFetch to retrieve the latest guidelines from a raw GitHub URL before each review. Without network access, it cannot load the rules and perform the check.

What output format does the docs review produce?▼

Findings are output in a terse file:line format, with each violation pointing to the exact location in the reviewed file. The precise format instructions come from the fetched guidelines content.