What file types can this skill analyze?

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

Where are the approved terms and rules stored?

Rules are defined in a reference file located at references/terminology-rules.md, which includes approved terms, variants to avoid, and formatting guidelines.

Can this skill identify inconsistencies if a term isn't in the rules list?

Yes, it performs internal consistency checks to ensure that if a new term is introduced, it is used the same way throughout the entire document.

What is the difference between Error and Warning levels?

Errors represent direct contradictions to the approved terminology list that must be fixed, while Warnings highlight internal inconsistencies that should be reviewed for clarity.

Documentation Terminology Validator

Name: Documentation Terminology Validator
Author: ekline-io

byekline-io

•

Learning & Documentation

Enforces consistent language and branding across documentation by validating files against approved terminology rules and style guides.

The Terminology skill is a specialized tool for technical writers and developers designed to maintain a unified voice and high editorial standards. By cross-referencing your documentation files against a custom ruleset, it identifies prohibited terms, incorrect product capitalization, and inconsistent technical jargon. It generates detailed reports with severity levels, helping teams eliminate branding errors and improve the readability of technical content across Markdown, MDX, and RST formats.

Key Features

01Structured reporting with Error, Warning, and Info severity levels

02Detection of prohibited terms and non-inclusive language

03Automated cross-referencing against custom terminology rules

04Internal consistency checks for recurring terms within a single file

05Support for Markdown, MDX, RST, AsciiDoc, and HTML files

062 GitHub stars

Use Cases

01Auditing legacy documentation for outdated or prohibited technical terms

02Standardizing product and feature name capitalization before a release

03Automating style guide enforcement during the technical review process

Key Features

01Structured reporting with Error, Warning, and Info severity levels

02Detection of prohibited terms and non-inclusive language

03Automated cross-referencing against custom terminology rules

04Internal consistency checks for recurring terms within a single file

05Support for Markdown, MDX, RST, AsciiDoc, and HTML files

062 GitHub stars

Use Cases

01Auditing legacy documentation for outdated or prohibited technical terms

02Standardizing product and feature name capitalization before a release

03Automating style guide enforcement during the technical review process