Percerno Skillsbeta
← everything it can do · compliance

Writing Guidelines TEXT

Reviews documentation or prose files for compliance with specific writing guidelines fetched from a remote source. Outputs a list of violations in a terse file:line format.

2 uses this weeksource vercel-labslicence MIT
Quality gate: FAIL · better answers · measured 2026-10-24
Blind-judged against the bare model on 2 requests: average lift -9.5 points (specificity, structure, method, fit).
won 0/2, lift -9.5, tokens ×767.36
Security scan: clean · 2026-10-24 · 1 files · ran in sandbox
no network calls, shell tricks, credential access or instruction tampering found in its files.

Try asking

Say it in your own words; the assistant finds this recipe by itself. Examples:

“Gennemgå min README.md i forhold til skriveregnlerne.”
“Tjek tonen i onboarding-dokumentationen i /docs/guides.”
“Auditér den nye blogindlæg for stiloverholdelse.”
“Please review my README.md against the writing guidelines.”
“Check the tone of the onboarding docs in /docs/guides.”
“Audit the new blog post for style compliance.”
Try this skill from Claude, ChatGPT or a chat on your own page. Free plan, no credit card.Get started free

Good for

writing-guidelinesstyle-checkdocumentationprose-auditvoice-tonecompliancereviewmarkdown

Not for

Do not use this skill for general grammar or spelling checks that do not rely on a specific external style guide; use a standard proofreading or grammar-checking skill instead. It is not for content strategy, structural editing, or factual accuracy verification. Avoid using it for code review or non-prose file types.

Details

When it is the right choice

Use this skill when a user wants to check their documentation, blog posts, or other prose against a specific set of writing standards or a style guide. It is appropriate for requests to audit voice, tone, or specific stylistic rules in text files. It is ideal for ensuring consistency in technical documentation or marketing copy.

The full recipe the assistant reads

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.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: 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.

Files in this skill (1)
  • SKILL.md
Where it comes from

Vendored from vercel-labs/agent-skills, commit 063bee94c3f4, path skills/writing-guidelines, licence MIT. The upstream licence file ships inside the skill.