documentation-expert

Analyzes and improves documentation structure, cohesion, navigation, and readability using research-driven patterns.

3|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/trudyan141/my-antigravity-agents-kit --skill documentation-expert-trudyan141
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: documentation-expert
Source: https://github.com/trudyan141/my-antigravity-agents-kit/tree/main/templates/.agent/skills/documentation-expert
Command: npx skills add https://github.com/trudyan141/my-antigravity-agents-kit --skill documentation-expert-trudyan141

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Documentation often suffers from deep navigation hierarchies, inconsistent terminology, broken links, poor audience targeting, and outdated content. This Skill diagnoses these documentation anti-patterns and applies proven information architecture fixes. ## Core Features & Use Cases - Structure Analysis: Detects navigation depth issues, oversized documents, and orphaned pages, then applies fixes like the Diátaxis framework or hub-and-spoke models. - Content Quality Review: Identifies cohesion problems, terminology inconsistencies, missing transitions, and undefined jargon across Markdown docs. - CLI Validation: Runs markdownlint-cli and markdown-link-check via npx to catch formatting issues and broken internal links. - Use Case: You inherit a project with a sprawling docs/ folder. Use this Skill to audit the structure, flatten deep navigation, fix broken links, and standardize terminology before a major release. ## Quick Start Review the documentation in my docs folder and fix any structural, navigation, or readability issues you find.

Frequently Asked Questions about documentation-expert

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

FAQPage Schema
How do I fix documentation with too many navigation levels?

Flatten navigation to a maximum of 2-3 levels by consolidating nested pages, or adopt a hub-and-spoke model where overview pages link to focused sub-pages. The Diátaxis framework also helps by organizing content into tutorials, how-to guides, reference, and explanation.

How to find broken links in Markdown documentation?

Run markdown-link-check via npx against your Markdown files to detect broken internal and external links. You can also write a shell loop that extracts link targets from each file and verifies the referenced paths exist.

What is the Diátaxis framework for documentation?

Diátaxis is a documentation architecture that splits content into four types: tutorials (learning-oriented), how-to guides (task-oriented), reference (information-oriented), and explanation (understanding-oriented). It prevents mixed-purpose documents that confuse readers.

Does markdownlint work without installing it globally?

Yes, run markdownlint-cli through npx so no global installation is required. You can disable overly strict rules like MD013 (line length), MD033 (inline HTML), and MD041 (first line heading) for practical defaults.

Why does documentation feel inconsistent across pages?

Inconsistency usually comes from mixed terminology (e.g., 'setup' vs 'set-up'), missing transitions between sections, and undefined acronyms. Audit term frequency with grep, add transitional sentences, and define acronyms on first use.

When should I split a long documentation page?

Split documents exceeding roughly 3,000 words or covering multiple distinct tasks. Create a hub page linking to focused sub-pages so each document serves one clear purpose and stays scannable.