skills.rest
ferrarifankid04
ferrarifankid04COMMUNITY
Explore all skills by this author →
GitHub

writing-guidelines

Review documentation and prose files against fetched writing style guidelines.

Updated Aug 6, 2026
Search Tags:#linting#writing#markdown#style guide#voice and tone#docs review#prose audit
One-click install
npx skills add https://github.com/ferrarifankid04/ai-skills-public --skill writing-guidelines-ferrarifankid04
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-guidelines
Source: https://github.com/ferrarifankid04/ai-skills-public/tree/main/claude-code/skills/writing-guidelines
Command: npx skills add https://github.com/ferrarifankid04/ai-skills-public --skill writing-guidelines-ferrarifankid04

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping documentation consistent with a team's writing style guide is tedious manual work. This Skill automates prose audits by fetching the latest writing guidelines and checking your files against every rule, outputting precise findings. ## Core Features & Use Cases - Fresh Guideline Fetching: Retrieves the latest rules from the vercel-labs writing-guidelines source URL before each review, so checks never go stale. - File and Pattern Review: Accepts a file path or glob pattern argument and audits all matching docs for voice, tone, and style compliance. - Terse Findings Output: Reports violations in a compact file:line format for quick triage and fixes. - Use Case: Before publishing a docs update, run a review across your Markdown pages to catch style violations like inconsistent tone or banned phrasing. ## Quick Start Ask the assistant to review your docs folder against the writing guidelines, for example by saying: review the files in docs/ for writing style compliance.

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 for writing style compliance?▼

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 before each review. This ensures the audit always uses the most current version of the style rules.

Can I review multiple files or a whole docs folder at once?▼

Yes, you can pass a file pattern as the argument to review multiple matching files in one run. If you provide no argument, the skill asks which files you want reviewed.

Does this skill work offline or without network access?▼

No, it requires network access because it fetches the latest guidelines from a remote GitHub URL via WebFetch before each review. Without connectivity, the rules cannot be retrieved.

What output format do the writing review findings use?▼

Findings are output in a terse file:line format, with each violation pointing to the exact file and line number. The fetched guidelines define the precise output format instructions.

Related Skills

Explore More Content & Communication Skills→
kellymearskellymears

comms

Draft emails, Slack messages, blog posts, and markdown in the user's authentic voice.

Community
Intermediate
ThalesGroupThalesGroup
19

docs-publish-github-pages

Inspect and patch GitHub Pages docs publishing workflows.

Official
Advanced
ghalacticghalactic

google-developer-style-guide-naming-terminology

Enforce Google developer documentation style guide capitalization, abbreviations, spelling, and grammar.

Official
Advanced
htlin222htlin222
77

vale

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

Community
Intermediate