Skills for technical writers to give their AI agents, so they can check and improve documentation.
npx skills@latest add GitbookIO/docs-skills- ai-readiness — Check and fix docs pages so AI assistants and retrieval systems can chunk, retrieve, and quote them.
- humanizer — Review or rewrite AI-sounding docs, release notes, and READMEs so they read like a skilled technical writer wrote them.
- seo-aeo-documentation — Create, edit, or review docs for content-level SEO and AEO without sacrificing readability or accuracy.
- openapi-drift-checker — Compare your docs against an OpenAPI spec and report inconsistencies.
- broken-link-checker — Find broken, redirected, and fragile links and anchors.
- terminology-checker — Build a glossary from your docs and flag places that use different words for the same concept.
- style-guide-builder — Build a style guide from your existing docs, surfacing inconsistencies as decisions to make.
- style-guide-to-skill — Turn a finished style guide into a skill that writers and agents can use.
- code-sample-checker — Verify code samples are valid, current, and consistent.
- docs-freshness-audit — Find pages that went stale after product changes and releases.
- accessibility-checker — Check alt text, heading order, link text, and other content accessibility issues.
- information-architecture-review — Review navigation, structure, duplication, and gaps.
- release-notes-writer — Draft user-facing release notes from PRs, commits, and tickets.
MIT