skills.rest
Debindenny
DebindennyCOMMUNITY
Explore all skills by this author →
GitHub

writing-guidelines

Review documentation files against fetched writing style guidelines and report violations.

Updated Aug 11, 2026
Search Tags:#documentation#voice and tone#writing guidelines#docs review#style review#prose audit
One-click install
npx skills add https://github.com/Debindenny/travelplanner-community- --skill writing-guidelines-debindenny
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-guidelines
Source: https://github.com/Debindenny/travelplanner-community-/tree/main/travel-planner/agent-skills/skills/writing-guidelines
Command: npx skills add https://github.com/Debindenny/travelplanner-community- --skill writing-guidelines-debindenny

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Maintaining consistent voice, tone, and style across documentation is hard when style rules live in a separate handbook. This Skill fetches the latest writing guidelines and audits your prose files against every rule automatically. ## Core Features & Use Cases - Fresh Rule Fetching: Retrieves the latest writing guidelines from the source URL before each review, so audits always use current rules. - File and Pattern Audits: Reviews specified files or glob patterns against all rules in the fetched guidelines. - Terse Findings Output: Reports violations in a compact file:line format for quick triage and fixing. - Use Case: Before publishing a docs update, ask for a review of your changed Markdown pages to catch voice, tone, and style violations against the team writing handbook. ## Quick Start Review the files in my docs folder 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 review my docs against writing style guidelines?▼

Provide a file path or glob pattern, and the Skill fetches the latest guidelines from the source URL, reads your files, and checks them against every rule. Findings are reported in a terse file:line format.

What files can I check for writing style compliance?▼

You can check any prose or documentation files by passing a specific file path or a pattern. If you do not specify files, the Skill asks which files you want reviewed.

Does the writing guidelines review use the latest rules?▼

Yes. The Skill fetches fresh guidelines from the source URL before each review using WebFetch, so audits always reflect the current version of the writing handbook rather than cached rules.

What output format does a writing style audit produce?▼

Findings are output in a terse file:line format, with each violation pointing to the exact location in the reviewed file. The precise format is defined by the fetched guidelines content.

What happens if I run the review without specifying files?▼

If no file or pattern argument is provided, the Skill prompts you to specify which files to review before proceeding with the guidelines fetch and audit.

Related Skills

Explore More Content & Communication Skills→
upboundupbound

upbound-docs-gen

Generate Upbound Spaces and UXP documentation drafts as Markdown files.

Official
Advanced
ThalesGroupThalesGroup
19

docs-publish-github-pages

Inspect and patch GitHub Pages docs publishing workflows.

Official
Advanced
Miosa-osaMiosa-osa
226

verify

Validate knowledge base structure, links, and abstract fidelity.

Official
Advanced
htlin222htlin222
77

vale

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

Community
Intermediate