skills.rest
danielbere1973
danielbere1973COMMUNITY
Explore all skills by this author →
GitHub

writing-guidelines

Reviews documentation files against fetched writing guidelines and reports violations in file:line format.

Updated May 15, 2026
Search Tags:#documentation#markdown#voice and tone#writing guidelines#docs review#style check#prose audit
One-click install
npx skills add https://github.com/danielbere1973/promoar --skill writing-guidelines-danielbere1973
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-guidelines
Source: https://github.com/danielbere1973/promoar/tree/main/.agents/skills/writing-guidelines
Command: npx skills add https://github.com/danielbere1973/promoar --skill writing-guidelines-danielbere1973

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Maintaining consistent voice, tone, and style across documentation is difficult when guidelines live in a separate handbook. This Skill automates prose audits by fetching the latest writing guidelines and checking your files against every rule. ## Core Features & Use Cases - Fresh Guideline Retrieval: Fetches the latest rules from the vercel-labs writing-guidelines repository before each review, so audits never use stale standards. - File and Pattern Review: Accepts a specific file or glob pattern as an argument, or prompts you for targets when none are given. - Terse Findings Output: Reports violations in a compact file:line format for quick navigation and fixing. - Use Case: Before publishing a new docs page, ask for a review to catch tone inconsistencies, style violations, and handbook rule breaches in one pass. ## Quick Start Ask the assistant to review docs/guide.md against the writing guidelines and list any violations.

Frequently Asked Questions about writing-guidelines

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

FAQPage Schema
How do I check my documentation 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 compact file:line format for quick fixes.

How do I review docs for voice and tone consistency?▼

Invoke the Skill with the docs files you want audited. It retrieves the current voice and tone rules from the vercel-labs writing-guidelines repository and flags any passages that violate them.

Does the writing guidelines review use the latest rules?▼

Yes. The Skill fetches guidelines fresh from the source URL on every run using WebFetch, so reviews always apply the most current version of the handbook rather than cached rules.

What happens if I do not specify files to review?▼

The Skill prompts you to provide the files or pattern to review. It requires a target file or glob pattern argument before it can run the guidelines check.

What output format does the writing review produce?▼

Findings are output in a terse file:line format as specified by the fetched guidelines. Each violation points directly to the location in the source file that needs attention.

Related Skills

Explore More Content & Communication Skills→
HugoRCDHugoRCD
1.8k

write-evlog-content

Reviews and rewrites evlog documentation, blog, landing, and skill prose against voice rules and AI-tell detection.

Community
Advanced
juicesharpjuicesharp
730

amend

Applies failing grade-panel verdict findings to surgically revise one artifact in place.

Community
Advanced
elasticelastic
71

docs-check-style

Validate documentation content against the Elastic style guide with Vale.

Official
Intermediate
htlin222htlin222
77

vale

Run Vale prose linter on markdown and text files to identify and auto-fix writing issues.

Community
Intermediate