Skills

The agent skills Blume ships — playbooks that teach a coding agent like Claude Code, Codex, or Cursor to build and maintain a Blume docs site.

Blume ships agent skills — playbooks that teach a coding agent (Claude Code, Codex, Cursor) how to do a Blume-shaped job without you explaining it. They live on GitHub in the repo’s skills/ folder and are bundled in the installed package under skills/, so any agent can be pointed at a SKILL.md directly.

Blume

The core skill. It teaches the agent what Blume is and how to scaffold, write, and configure a site — filesystem-derived navigation, the config schema, content components — and points it at the full docs bundled in the installed package (the docs/ directory inside blume, resolved from wherever your package manager installs it — in a pnpm monorepo that’s the depending workspace’s node_modules, not the repo root). Install it in any project where an agent helps you build your docs:

npx skills add haydenbleasel/blume

Migration

blume-migrate moves an existing docs site to Blume from Mintlify, Docusaurus, GitBook, MkDocs, ReadMe, the other named sources, or any other framework. It targets idiomatic Blume rather than a line-by-line port, with a mapping reference for each named framework, a redirect for every URL that moves, and a report of anything it drops. The quickest way to run it is blume migrate, which detects your framework and opens Codex or Claude Code on the copy bundled in the package. To use it from another agent, install it:

npx skills add haydenbleasel/blume --skill blume-migrate

Self-updating docs

blume-update-docs keeps your docs in sync with the product they document. On each run — typically from a schedule you configure in your agent runner — it audits recently merged PRs, changelogs, config schemas, and CLI help against the docs content, updates only pages that are factually stale (feature-flagged work is ignored), verifies with blume build and blume validate, and opens or updates a blume/* pull request. If nothing drifted, it reports a clean no-op instead of opening a noisy PR.

npx skills add haydenbleasel/blume --skill blume-update-docs

Blume doesn’t host the automation — wire the skill into a scheduled task in Claude Code, a Codex or Cursor automation, or plain cron, with permission to read repo history and open PRs. A typical weekly prompt:

Use the blume-update-docs skill. Review the PRs merged within the last 7 days and compare them to the docs content. Ignore work behind feature flags. If docs need updates, make them, verify the docs build, and open a blume/* PR. If not, report what you checked and do not open a PR.

Writing your site’s skill

blume-write-skill writes the agent skill for your own docs: one SKILL.md, grounded in the docs, that teaches a coding agent to use your product — setup, core concepts, common tasks, and gotchas — with each topic linked to its page. It takes the place of the page map Blume generates at /skill.md. The quickest way to run it is blume skill, which works out where the skill goes and opens Codex or Claude Code on the copy bundled in the package:

blume skill --claude   # or --codex

To use it from another agent, install it:

npx skills add haydenbleasel/blume --skill blume-write-skill