Your skill, captured.
A markdown document, a folder of scripts — whatever shape your skill takes. Botdocs treats it as a first-class artifact, ready to share.
MarkdownScriptsExamples
Bundle your team's agent skills, ship them like a package, sync them like git. They land in the right place for Claude, Cursor, Codex, Copilot — 10 agents in all — automatically. Onboard a new hire or rebuild your own laptop with the same command.
Not a developer? See the no-terminal tour for your team →
Scroll to see how a single markdown file becomes shared infrastructure for every AI agent your team uses.
A markdown document, a folder of scripts — whatever shape your skill takes. Botdocs treats it as a first-class artifact, ready to share.
Run a single command and your skill goes from your laptop to a shareable URL — versioned, attributed, discoverable.
Every skill gets its own page. Teammates and the wider community can find it, read it, install it.
Each teammate picks the assistant that fits their workflow — Claude, Codex, Cursor, or any agent. No vendor lock-in, no per-tool setup.
Improve the skill, bump the version, push. The cycle that lets a small team behave like a much larger one.
Stop downloading skills agent by agent. One `botdocs sync` propagates changes to every agent in your stack — OpenClaw, Hermes, Claude, Codex, Cursor, Cline.
No more "do you have the latest version?" — everyone on your team is always working from the same source of truth.
Each skill installs in every agent's native format and location.
Already have skills scattered across ~/.claude/skills, .cursor/rules, .codex? botdocs ingest pulls them in — helper scripts, templates and all — so your registry starts full. Review, tidy the titles, publish when ready.
Curate a playlist of skills. Anyone on your team installs them with one command — they land in the right place on disk for every agent, automatically.
Publish a new version and every installed copy notices. A quiet one-liner on shell open; botdocs sync applies clean updates and asks before touching local edits.
Open the personalized Library page to see what you have, what your team has, and what's new. Wire up a one-line shell hook and new terminals quietly tell you when updates are pending — silent when there's nothing to report.
# Quiet one-liner on shell open ↑ 2 botdocs updates pending — run botdocs sync $ botdocs sync ↓ @teamco/eng-skills 1.4.0 → 1.5.0 ↓ @teamco/runbooks 0.3.1 → 0.3.2 ✓ 2 updates applied cleanly $ botdocs list @teamco/eng-skills@1.5.0 @teamco/runbooks@0.3.2 @alice/code-reviewer@2.1.0
The official skill for turning a project, chat transcript, or folder of notes into a properly-structured BotDoc draft using your LLM.
Bootstraps an AI agent on the BotDocs CLI: ingest existing skills, search and install team libraries, sync, publish, and manage teams from the terminal across Claude, Claude Code, Cursor, Codex, Copilot, Windsurf, Gemini, Antigravity, OpenCode, and ChatGPT.
A personal work activity tracking system with automatic capture, manual annotations, AI summaries, and natural language queries.
A data visualization application specification covering data sources, charts, filtering, real-time updates, and exports.
A comprehensive approach to testing covering unit, integration, and e2e philosophy, what to test, and deployment confidence.
Generate a manual QA checklist for the current branch by pulling the linked Linear ticket's acceptance criteria. Use this skill whenever the user says "QA list", "/qa-list", "give me a QA list", "what should I QA", "what do I need to test", "build me a test plan", or any similar phrasing that asks for a manual testing checklist for the work on the current branch. Also trigger when the user is about to push, PR, or hand off a branch and wants to sanity-check what to verify. Parses the current branch name to find a Linear ticket ID (e.g. `trevor/CHA-123`), queries Linear via MCP, and converts acceptance criteria into a tappable inline markdown checklist. Falls back gracefully when AC is missing or the ticket can't be found — synthesizes a QA list from the description and/or the git diff against the base branch.
Bring in the skills you already have. Bundle them once. Install them anywhere, sync them forever.
Not a developer? See the no-terminal tour for your team →