mcpbeat

Writing Guidelines

nexu-io/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".

4k tokens
context cost
the whole folder, loaded on every use
3
files
instructions only
0
copies elsewhere
how many repositories repackaged it
83386
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/nexu-io/open-design --skill writing-guidelines

What comes with it

15 239 bytes besides the instruction
LICENSE
references/guidelines.md

The instruction itself

4 sections, as written by the author

Writing Guidelines

Review files for compliance with Writing Guidelines.

How It Works

  • Load the pinned guidelines from references/guidelines.md — this is the default, reproducible execution path
  • Optionally, fetch the latest guidelines from the upstream URL below and diff against the pinned snapshot to see if anything has changed
  • Read the specified files (or prompt user for files/pattern)
  • Check against all rules in the guidelines
  • Output findings in the terse file:line format

Guidelines Source

Default (pinned): The vendored copy at references/guidelines.md is the default execution path. It is a pinned snapshot of the upstream guidelines and guarantees the skill produces reproducible results in any runtime environment.

Upstream (live): For users who want the very latest rules, the live source is available at:

https://raw.githubusercontent.com/vercel-labs/writing-guidelines/main/command.md

Fetching the live version is optional — the pinned snapshot is always the baseline.

Usage

When a user provides a file or pattern argument:

  • Load references/guidelines.md as the default source
  • Optionally fetch the upstream URL to check for updates
  • Read the specified files
  • Apply all rules from the 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 nexu-io/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.