mcpbeat

Writing Guidelines

vercel-labs/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".

308 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
70 d ago
last touched
this folder, not the whole repository

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/vercel-labs/agent-skills --skill writing-guidelines

The instruction itself

4 sections, as written by the author

Writing Guidelines

Review files for compliance with Writing Guidelines.

How It Works

  • 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

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. The fetched content contains all the rules and output format instructions.

Usage

When a user provides a file or pattern argument:

  • Fetch guidelines from the source URL above
  • Read the specified files
  • Apply all rules from the fetched guidelines
  • Output findings using the format specified in the guidelines

If no files specified, ask the user which files to review.

How to use it

Copy the folder

Take vercel-labs/writing-guidelines from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

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.