How does the skill evaluate documentation quality?

It generates a compliance report with a numerical score based on voice, terminology, and formatting violations, categorized by high, medium, and low severity.

Which file formats does the Style Guide skill support?

The skill supports a wide range of documentation formats including .md, .mdx, .rst, .adoc, .txt, and .html.

What core style rules does the skill enforce?

By default, it enforces active voice, second-person perspective, present tense, and verb-first lead sentences, while banning subjective language like 'basically' or 'easily'.

Can this skill automatically fix my documentation errors?

Yes, it can auto-fix specific violations like removing prohibited phrases and converting headings to sentence case, while complex voice issues are flagged for manual review.

Style Guide Reviewer

Name: Style Guide Reviewer
Author: ekline-io

byekline-io

•

Content Management

Enforces consistent documentation voice, tone, and formatting rules across multiple file formats to ensure high-quality technical content.

The Style Guide skill provides an automated framework for maintaining professional standards across documentation repositories. It proactively validates content against specific rules—such as active voice, second-person address, and present tense—while scanning for prohibited phrases and formatting inconsistencies in headings and code blocks. By generating comprehensive compliance reports with severity-weighted scoring and offering auto-fix capabilities for common errors, it reduces manual editing time and ensures a unified brand voice across Markdown, MDX, and other technical document types.

Key Features

01Automated voice and tone validation (active voice, second person)

022 GitHub stars

03Detailed compliance reports with severity-rated violations

04Prohibited phrase detection and replacement suggestions

05Auto-fix capabilities for common style and formatting issues

06Structural formatting enforcement for headings and code blocks

Use Cases

01Automating the review process for new documentation pull requests

02Converting legacy documentation from passive to active voice and correcting heading cases

03Standardizing a documentation repository after multiple contributors have added content

Key Features

01Automated voice and tone validation (active voice, second person)

022 GitHub stars

03Detailed compliance reports with severity-rated violations

04Prohibited phrase detection and replacement suggestions

05Auto-fix capabilities for common style and formatting issues

06Structural formatting enforcement for headings and code blocks

Use Cases

01Automating the review process for new documentation pull requests

02Converting legacy documentation from passive to active voice and correcting heading cases

03Standardizing a documentation repository after multiple contributors have added content