domains / families / general / busabase
busabase
authentic
Use when managing Busabase workspace records, knowledge, apps, or skills through permission-aware ChangeRequests with auditable history.
When to use
- Use when the user asks to find or maintain records in a Busabase Base.
- Use when the user requests scoped workspace knowledge, app, or skill changes with traceable history.
- Use when the user needs to distinguish proposed content from canonical workspace data.
- Do not use it to operate a different database or to publish workspace content to external services.
When not to use
- Requires an available Busabase MCP connection, sufficient access, and a confirmed workspace. It does not provision accounts, authenticate a plugin, or install a CLI.
- Tool names, fields, and supported operations vary by deployment. Always inspect live schemas; do not promise unsupported review flags, write behavior, or URL formats.
- Does not bypass permissions, decide approvals, publish private data, or automatically generate bearer links.
- App deployment, arbitrary scripts, SDK coding, and full CLI workflows are outside this version's scope.
- Structural checks do not prove runtime efficacy. A hosted integration read does not establish local Claude plugin OAuth or end-to-end write behavior.
Skill page
Source