documentation-expert

Diagnose documentation structure, cohesion, and discoverability problems.

Updated Jan 2, 2026
One-click install
npx skills add https://github.com/yuhle-qug/Parking_Management_System --skill documentation-expert-yuhle-qug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: documentation-expert
Source: https://github.com/yuhle-qug/Parking_Management_System/tree/main/.agent/skills/documentation-expert
Command: npx skills add https://github.com/yuhle-qug/Parking_Management_System --skill documentation-expert-yuhle-qug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams improve documentation quality by diagnosing structure, cohesion, and discoverability problems.

Core Features & Use Cases

  • Documentation structure analysis and audits to identify orphaned sections and excessive depth
  • Cohesion and readability improvements through improved transitions and consistent terminology
  • Audience-targeted guidance with clarity checks and governance for maintenance

Quick Start

Run a documentation audit on your repository and generate a prioritized improvements plan for existing docs.

Frequently Asked Questions about documentation-expert

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

FAQPage Schema
How do I audit documentation structure for orphaned sections and excessive depth?

Run a documentation audit to diagnose structure problems, identifying orphaned sections and excessive depth to generate a prioritized improvements plan for existing docs.

What is the best way to improve documentation cohesion and readability?

Improve documentation cohesion by analyzing content for readability problems, applying consistent terminology, and adding transitions to ensure clarity and usability for the target audience.

How do I set up governance and maintenance routines for internal knowledge bases?

Establish documentation governance by enforcing maintenance routines, audience awareness, and consistent terminology across internal knowledge bases to ensure long-term content discoverability.

Can I use this approach to audit API docs and user guides?

Yes, you can audit API docs and user guides to diagnose discoverability problems, enforce navigation aids, and generate prioritized improvements for content clarity.

When do I need documentation governance for audience-targeted clarity?

You need documentation governance when maintaining API docs or internal knowledge bases, requiring audience-targeted guidance, clarity checks, and consistent terminology to prevent content discoverability problems.