docs-skills

npx skills add Docsbook-io/docs-skills --skill '*'

Find your pain#

Scan the left column. Find yours. Run the command.

😫 "My docs are a mess and I don't know where to start"#

npx skills add Docsbook-io/docs-skills --skill docs-analyze

"Audit my docs and give me one prioritized report"

🚀 "I have no docs — or the wrong ones"#

npx skills add Docsbook-io/docs-skills --skill docs-create

"Turn this GitHub repo into a live docs site"

📊 "I'm guessing what to write next"#

Real user signal instead of opinion.

npx skills add Docsbook-io/docs-skills --skill docs-gap-finder

"What are users searching for but not finding?"

🔁 "I keep doing the same maintenance by hand"#

Install once, runs forever.

npx skills add Docsbook-io/docs-skills --skill docs-sync

"Stop my docs from drifting out of sync with the code"

📦 "Now ship it"#

🧭 "I need a plan before I write anything"#

Install (30 seconds)#

Works in Claude Code, Cursor, Codex, Copilot.

npx skills add Docsbook-io/docs-skills --skill '*'

One skill only:

npx skills add Docsbook-io/docs-skills --skill docs-analyze

Then ask in plain language. No flags, no config — the skill fires from your request:

"Audit my docs and give me one prioritized report" "Turn this GitHub repo into a live docs site" "Which pages are users searching for but not finding?" "Translate my docs into 15 languages"

Before / after#

Full catalog#

52 skills, 7 categories. Browse live: docsbook.io/skills.

Plan / MCP columns. Most skills are free and run on any agent with no account. MCP marks the few that genuinely operate a hosted workspace (branding, languages, webhooks) — they fall back to printed instructions when it's absent. PRO / PRO+ marks skills that read production analytics.

How it works#

A skill is a reusable regulation — Workflow + Guardrails + Acceptance Criteria — not a one-off prompt.

Each skill states a need ("get the list of pages in scope and read their content") and how to reason about it, rather than a hardcoded way to fetch it. The agent satisfies the need with whatever it has connected:

AI Tool (Claude Code / Cursor / Codex / Copilot)
        │
        ▼
  docs-skill runs  ──▶  states the need + how to think
        │
        ├─ nothing connected ──▶  grep / find over the docs folder
        ├─ markdown-lsp       ──▶  semantic / graph search, self-hosted
        └─ Docsbook MCP       ──▶  same capability in the cloud + workspace settings
        │
        ▼
  Audit report / generated files / configured workspace

The agent sees what's available and picks the cheapest path.

The catalog's contract on tool names. A skill names the need and the acceptance criteria. A platform tool is named only where calling it is the goal of the step — set the branding, register a webhook, flip a workspace flag — and never where it's merely one way to fetch data. So "the questions readers asked that got no answer" stays a need: an agent with nothing connected greps the logs, and one with the MCP connected gets the same answer as a typed list. That's what makes a skill run on a bare agent and get sharper — not narrower — when a platform is attached.

Modes — what a skill is allowed to touch#

Every skill declares a mode, so you know before you hand it your docs whether it edits files:

CI enforces it: a skill without a valid mode does not ship.

Optional acceleration#

# Optional cloud transport
mcp add --transport http https://docsbook.io/api/mcp/server

The cloud transport runs markdown-lsp for you — self-hosted and cloud are the same capability, your choice of where it runs. The bare grep/find fallback always works.

CLI reference#

Powered by the skills CLI:

npx skills add Docsbook-io/docs-skills --skill '*'        # install the whole catalog
npx skills add Docsbook-io/docs-skills --skill docs-seo   # install one skill
npx skills add Docsbook-io/docs-skills -a claude-code -a cursor --skill '*'   # target specific agents
npx skills list                                           # list installed skills
npx skills find <keyword>                                 # search for a skill
npx skills update                                         # update installed skills

Contributing#

Skills are plain Markdown files under skills/ — either skills/<name>/SKILL.md or skills/<category>/<name>/SKILL.md; the category comes from frontmatter, not the path. To add one:

1. Create skills/your-skill/SKILL.md following the schema in schema/
2. Run pnpm build-index to regenerate index.json
3. Open a PR

The catalog is intentionally minimal — one file per skill, no runtime dependencies.

License#

MIT © 2024 Dan Bondarev / docsbook.io