Botz Skills

Consume governed Agent Skills and subagent definitions from the hosted botz.ai MCP server, with the plumbing hidden from the user. Docs: https://zotoio.github.io/zoto-agents/botz-skills/

• Locate skills (skill_search) and subagents (agent_search) semantically and download them as token-frugal CRUX Compress bundles via skill_get_compressed / agent_get_compressed (incorporating SKILL.md + all references/ and scripts/ in one call; or plain Markdown via skill_get + skill_resource_get on demand; agent_get for installable client definitions).
• Zero drift: every consumed artifact is pinned by permanent guid + version in .botz/skills.lock.json. Server-side forks, combinations, or evolutions never change what a pinned consumer receives.
• Evolution aware: skill_updates is checked once per session and the user is told about enhancements (changelog included). Saying "auto accept skill updates" flips the lock to "evolution": "auto".
• Self-extending: uncovered needs go through skill_request / agent_request; creation is conversational, so the server can ask clarifying questions mid-request.

Install

/add-plugin zoto-botz-skills

Connection

The plugin ships an MCP server entry named botz:

{ "mcpServers": { "botz": { "url": "https://mcp.botz.ai/mcp" } } }

https://mcp.botz.ai/mcp uses MCP OAuth: your client opens a browser sign-in the first time it connects. There are no tokens or environment variables to set, and none are stored in the plugin. To use a self-hosted botz-mcp server, override the botz entry's url in your own MCP config.

Headless / CI

IDE clients never need a token. API keys are only for non-interactive callers (CI jobs, scripts, servers): mint a bzt_ key in the botz management console at /admin → IAM · API tokens, store it as a CI secret, and send it as an Authorization: Bearer header:

# placeholder only - read the key from your CI secret store
curl -sS https://mcp.botz.ai/mcp \
  -H "Authorization: Bearer $BOTZ_API_KEY" \
  -H "Content-Type: application/json" -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Contents

Keeping the skill in sync

The skill is authored in zotoio/botz-mcp. After it changes there, copy skills/botz-mcp/SKILL.md into plugins/zoto-botz-skills/skills/botz-mcp/, bump the version in all four manifests, and add a CHANGELOG entry.