GitbookIO

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…

Write, author, edit, and format GitBook documentation pages in Git-synced repos, IDEs, or any text editor. Use whenever a task involves creating or editing a GitBook markdown page, writing or updating a README.md or SUMMARY.md, inserting a hint, tab, stepper,…

Create and maintain GitBook documentation sites end-to-end — design structure from source content, scaffold a Git monorepo, set up the GitHub/GitLab remote, drive the GitBook API (REST or MCP) to create the site/sections/spaces, apply branding, and hand off…

Drive an end-to-end GitBook docs review flow from Claude Code by calling the GitBook REST API directly with curl (no CLI) — create a change request, push content (update an existing page AND create a new page), request reviewers, notify Slack, then pull…

Review GitBook change requests from Claude Code by calling the GitBook REST API directly with curl (no CLI) — the reviewer-side companion to cr-create (the authoring side over the same API). Discover the change requests that need review (filter by who opened…

Build, develop, and publish GitBook integrations — apps that run inside GitBook to add custom blocks, react to events, connect external services via OAuth, and extend the editor. Use this skill whenever a task involves the GitBook integrations platform:…

Author, configure, structure, and troubleshoot OpenAPI/Swagger API reference documentation in GitBook. Use this whenever a task involves a GitBook OpenAPI block or `{% openapi %}` block, adding or updating an OpenAPI/Swagger spec in GitBook (by file or URL,…

Write a concise, product-focused PR description from the changes and available discussion. Use when asked for a PR summary or description.

Audit GitBook integrations for script injection, sensitive-data access, unsafe requests, authorization gaps, and manifest or dependency risk. Use for a requested integration security review, not routine feature work.

Create and maintain entire GitBook documentation sites end-to-end — design the site structure from source content, scaffold a Git repository in monorepo layout, set up the GitHub/GitLab remote, drive the GitBook REST API to create the site/sections/spaces,…