writing-guidelines

Identify writing guideline deviations across documents and output machine-friendly findings.

Updated Jan 17, 2026
One-click install
npx skills add https://github.com/lDuang/mcp-skill-registry --skill writing-guidelines
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-guidelines
Source: https://github.com/lDuang/mcp-skill-registry/tree/main/skill/writing-guidelines
Command: npx skills add https://github.com/lDuang/mcp-skill-registry --skill writing-guidelines

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review docs for compliance with specified Writing Guidelines to improve clarity, tone, and consistency across content.

Core Features & Use Cases

  • Guideline Compliance Checks: Identify deviations in voice, style, grammar, terminology, and structure.
  • Guideline Sourcing: Fetch the latest rules from a trusted guidelines source and apply them to your content.
  • Use Case: Run a quick audit on a product docs page to surface tone mismatches and terminology inconsistencies.

Quick Start

Provide the target documents or patterns and ask me to audit them against the latest writing guidelines.

Frequently Asked Questions about writing-guidelines

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

FAQPage Schema
How do I audit my documentation for tone and style consistency?

To audit documentation for tone and style consistency, provide the target documents to apply rule-based validation against fetched writing guidelines. It flags voice, grammar, and prose deviations across multiple files in a terse, machine-friendly format.

Can I check multiple files for writing guidelines compliance at once?

Yes, you can check multiple files for writing guidelines compliance at once. The audit applies checks to prose across multiple files, pages, and blocks to surface terminology inconsistencies and structural deviations dynamically.

How does dynamic guideline fetching work for prose reviews?

Dynamic guideline fetching works for prose reviews by sourcing the latest rules from a trusted guidelines source. It applies these fetched rules to your content to identify deviations in voice, style, and grammar.

What is the output format for a style-check audit?

The output format for a style-check audit is a terse, machine-friendly structure. It outputs findings that flag specific voice, tone, grammar, style, and consistency issues found within the provided documents.

Do I need to manually provide writing rules to review my docs?

You do not need to manually provide writing rules to review your docs. The process supports dynamic guideline fetching to automatically retrieve the latest rules from a trusted source and validate your content against them.

What is the best way to surface terminology inconsistencies in product docs?

The best way to surface terminology inconsistencies in product docs is to run a guideline compliance check. It identifies deviations in terminology and structure across your content and reports them in a machine-friendly format.