Enforces terminology, prose, and verification conventions for the beads Mintlify documentation site.
npx skills add https://github.com/steveyegge/beads --skill beads-docs
Please help me install this Agent Skill. Skill: beads-docs Source: https://github.com/steveyegge/beads/tree/main/.claude/skills/beads-docs Command: npx skills add https://github.com/steveyegge/beads --skill beads-docs
Writing or editing the beads user documentation (the Mintlify site under docs/) without a shared style guide leads to inconsistent terminology, prose that drifts from the actual CLI behavior, hand-edited generated files, and broken navigation. This Skill encodes the project's canonical concept model, required vocabulary, formatting rules, and verification gates so every docs change stays accurate and consistent.
Use the beads-docs conventions to review and rewrite the getting-started page under docs/ so it matches the canonical terminology and passes the docsync verification gates.
High-intent search queries and answers about installing and using this skill.
Follow the house style: lead with the problem before mechanics, use the canonical terminology (bead, proto, molecule, gate), keep pages single-purpose, and run the verification gates like go test ./test/docsync and a local Mintlify preview before committing.
Rename the concept in prose only while preserving every literal the program prints, including command names, flags, config keys, and code fence output. Never hand-edit generated files; change the Cobra strings in cmd/bd and regenerate the CLI docs instead.
No. Generated files like docs/cli-reference/* and docs/CLI_REFERENCE.md must be changed at their source: edit the Short, Long, and Example strings in the Go command definitions, then run ./scripts/generate-cli-docs.sh to regenerate them.
Run go test ./test/docsync for navigation and link consistency, ./scripts/generate-cli-docs.sh --check for generated docs freshness, ./scripts/check-doc-freshness.sh for review markers, and preview the site with make docs-dev at localhost:3000.
Add a redirect in the redirects array of docs/docs.json, rewrite inbound links across the whole repo including README and engdocs, and if the bd binary prints the old path, fix the Go source and regenerate rather than creating a pointer stub.
AnsteorraManage tasks in a distributed, git-backed graph issue tracker.
openonionAutomate end-to-end feature releases from code changes to PyPI.
ajbareaVerify documentation claims against repository code and configuration.
GozeiFormat and beautify Markdown documents with configurable style guides.
