Copy this prompt into the AI assistant you're using.
Follow https://skillsmp.com/skill-install/prompt.md to install Agent Skills from https://github.com/GitbookIO/docs-skills.Loading the repository README…
Showing 13 of 13 collected skills.
Planned: review documentation for content accessibility issues, including missing or poor image alt text, skipped heading levels, non-descriptive link text, color- or position-only instructions, inaccessible tables, and unexplained abbreviations. Use when a…
Check or fix documentation pages for AI readability, so AI assistants, Ask AI, RAG pipelines, and other LLM retrieval systems can retrieve, chunk, and quote them accurately. Use when a writer asks whether docs are AI-ready or LLM-ready, how pages will chunk…
Planned: find broken, redirected, and fragile links in a documentation repo or published docs site, including relative links, heading anchors, images, and external URLs, and propose fixes. Use when a writer asks to check links, find 404s, fix dead links, or…
Planned: verify that code samples in documentation are syntactically valid, use current APIs and package versions, are consistent across languages, and run where possible. Use when a writer asks to test, validate, or update code snippets, examples, or…
Planned: find stale documentation by comparing pages against changelogs, release notes, version numbers, and last-updated history, and flag content that references removed, renamed, or outdated features. Use when a writer asks which docs are out of date, what…
Review or rewrite documentation and docs-adjacent copy (guides, reference pages, release notes, changelogs, READMEs) so it reads like a skilled human technical writer wrote it, without changing meaning, facts, terminology, code, links, or UI labels. Use when…
Planned: review the structure of a documentation set, including navigation, page grouping, content types, duplication, orphaned pages, and gaps, and recommend a clearer organization. Use when a writer asks to restructure docs, review navigation or a table of…
Planned: compare documentation pages against an OpenAPI specification and report drift such as missing or renamed endpoints, parameters, fields, enums, defaults, status codes, auth requirements, and stale examples. Use when a writer asks to check docs against…
Planned: draft clear, user-facing release notes and changelog entries from merged pull requests, commits, tickets, or internal notes, grouped by impact and written in the team's style. Use when a writer asks to write release notes, a changelog entry, or a…
Create, edit, or review product and technical documentation for content-level search engine optimization (SEO) and answer engine optimization (AEO) while preserving human readability, factual accuracy, and house style. Use when a docs task mentions SEO, AEO,…
Planned: help a docs team build a style guide from its existing documentation instead of a generic template. Extracts the conventions the docs already follow, presents inconsistencies as decisions to make, and asks about things the docs cannot show, such as…
Planned: convert a finished style guide into an Agent Skill (SKILL.md) that writers and AI agents can load to apply the guide while writing and reviewing docs. Use when a writer asks to turn a style guide into a skill, agent instructions, or rules for an AI…
Planned: build a glossary from existing documentation and flag places where different words are used for the same concept, inconsistent capitalization of product terms, and undefined jargon. Use when a writer asks to check terminology, build a glossary,…
Repository README source: README.md
Read the source README