Busabase Skills & Plugins

Agent Skills + plugins for Busabase — the approval-first knowledge base where AI proposes changes, a human reviews them, and only approved changes get merged.

One skill, four ways to install it — pick whatever your agent supports.

Install

skills (Claude Code, Cursor, Codex, … — evergreen)

npx skills add busabase/skills

Claude Code plugin

/plugin marketplace add busabase/skills
/plugin install busabase@busabase

Codex plugin

codex plugin marketplace add busabase/skills
codex plugin add busabase@busabase

MCP (any MCP-capable agent)

Point your agent at your workspace's Streamable-HTTP endpoint:

• Desktop / local: http://localhost:15419/api/mcp (no auth)
• Cloud: https://busabase.com/api/mcp (send Authorization: Bearer $BUSABASE_API_KEY)

The bundled .mcp.json wires the local endpoint by default; edit the url (and add an auth header) for Cloud.

All of these install the same busabase skill. It is small and evergreen: it reads your workspace base URL (and API key, on Cloud) from ~/.busabase/.env, and points at your workspace's live /api/v1/openapi.json for the full API.

To set up a workspace from scratch first, paste the onboarding prompt from your Busabase dashboard (Agent Skills button) — it walks your agent through connecting, seeding a first Base, and then running one of the install commands above.

Skills

Skill	What it does
busabase	Drive a Busabase workspace over HTTP: list Bases/records, propose ChangeRequests, and merge approved ones.

Repo layout

This one repo serves every install path above:

skills/busabase/SKILL.md              the skill (canonical) — used by `skills`, Claude Code, Buda
.claude-plugin/plugin.json            Claude Code plugin manifest (auto-discovers ./skills/)
.claude-plugin/marketplace.json       Claude Code marketplace listing
.agents/plugins/marketplace.json      Codex marketplace listing
plugins/busabase/.codex-plugin/plugin.json   Codex plugin manifest
plugins/busabase/skills/busabase/SKILL.md    Codex needs the skill INSIDE the plugin dir
                                             (a copy of the canonical one — keep in sync)
.mcp.json                             bundled MCP server (Streamable HTTP)
server.json                           official MCP Registry entry (remote → busabase.com/api/mcp)

Why the Codex copy? Codex only resolves a plugin from a plugins/<name>/ subdir and bundles only files inside that dir on install (symlinks and ../ paths are dropped). So the Codex plugin carries its own copy of the skill under plugins/busabase/skills/. Re-copy skills/busabase/ there whenever the canonical skill changes.

Publish to the official MCP Registry

brew install mcp-publisher                       # or grab the binary from the registry releases
mcp-publisher login dns --domain busabase.com --private-key <KEY>   # verifies the com.busabase/* namespace
mcp-publisher publish                            # publishes server.json — live immediately, no review

Bump version in server.json (and the plugin manifests) to ship an update.