Expert at organizing and managing documentation structure across projects. Auto-invokes when organizing documentation files, setting up documentation frameworks, creating documentation directories, managing doc site configurations, or establishing documentation standards for a project. Provides guidance on documentation architecture and tooling.
SkillScore77Maintained
Automatic
◆Doc Ops pack
Last verified 9/3/2026
What it changes
Passed 20 of 26 test cases with the skill, and 17 of 26 without it.
Without skill65%
With skill77%
Checks it passed that the model alone missed
Passes the --fix argument to the markdownlint hook.
Uses a docs/latest/ directory pointing to current version.
Uses create-docusaurus@latest docs classic to initialize the site.
and 1 more in the full report
3 fixed17 passed either way6 still failing0 broke
Pass-rate lift
+12 pp
Tokens
+101%
Agent turns
0%
Response time
-13%
Model gemini-3.6-flashMeasured 9/3/2026v120 of 26 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 3
Prompt
We want to set up pre-commit hooks to automatically check and fix markdown formatting across all doc files before commit. Which pre-commit repository and hook should we configure in `.pre-commit-config.yaml`?
What was checked, without and with the skill
Checked
Without skill
With skill
Configures igorshubovych/markdownlint-cli as the repository hook source.
Missed
Passed
Passes the --fix argument to the markdownlint hook.
Missed
Passed
case-13 · gemini-3.6-flash · 9/3/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md409 linessingle file
Managing Documentation Skill
You are an expert at organizing, structuring, and managing documentation across software projects.
When This Skill Activates
This skill auto-invokes when:
User asks about documentation structure or organization
User wants to set up documentation for a project
User needs to configure documentation tools (Sphinx, MkDocs, etc.)
User asks about documentation best practices for organization
User wants to restructure existing documentation
Documentation Architecture Patterns
Pattern 1: Simple Project (README-Centric)
Best for: Small projects, libraries, single-purpose tools
project/
├── README.md # Main documentation
├── CONTRIBUTING.md # Contribution guidelines
├── CHANGELOG.md # Version history
├── LICENSE # License file
└── docs/
└── api.md # API reference (if needed)
Pattern 2: Standard Project (Docs Directory)
Best for: Medium projects, applications with multiple features