← ClaudeAtlas

brain-toolslisted

Onboard YOUR tools into Symbiosis Brain tool-routing. Use when the user types /brain-tools, or asks to set up / onboard / configure / register their tools, MCP servers, or routing — e.g. "настрой мои инструменты", "set up tool routing", "добавь мои тулы в роутинг", "configure routing for my MCP servers". Lists the tools available in THIS install, auto-routes the ones it already knows, asks one short question per unknown tool, and writes a per-install override file so each user tailors routing to their own toolbox without editing package code.
Krill113/symbiosis-brain · ★ 0 · AI & Automation · score 72
Install: claude install-skill Krill113/symbiosis-brain
# Brain Tools — Routing Onboarding On-demand discovery skill (spec §7, C6). It surveys the tools available in *this* install, keeps the ones the shipped catalog already covers, and helps the user draft routes for anything new — then writes them to a per-install override that the routing engine merges on top of the package defaults. ## Universality (why this is data, not code) The Symbiosis Brain package ships a universal default catalog (`tool-routing.json`: web / registry / powershell / playwright / serena / catalog / debug). Another user with a different toolbox configures THEIR tools **without touching package code** — purely by data, via a per-install override file `tool-routing.local.json` in the vault (git-ignored, never indexed by `brain_search`). This skill is the friendly front-end that produces that file. ## When to use Run only on explicit request — `/brain-tools`, or when the user asks to set up, onboard, configure, or register their tools / MCP servers / routing. Do NOT trigger it on every session; routing already works from the defaults out of the box. This skill is for tailoring routing to a specific toolbox. ## Fail-open contract Every step degrades to a no-op rather than blocking: - Roster cache absent → fall back to a live `claude mcp list`; if that fails too, work from the built-ins alone. - `$SYMBIOSIS_BRAIN_VAULT` unset / unwritable → tell the user once and stop; do not crash. - User declines to answer for an unknown tool → skip that tool, keep