.claude/skills/sandbaseRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
Safely use or set up the SandBase MCP server in Antigravity, Trae, Qoder, WorkBuddy, or Pi. Use when a user asks one of these clients to use SandBase, connect SandBase, install or configure the SandBase MCP, diagnose whether SandBase is connected, or finish OAuth and stdio bridge setup without expos
These states come from the source or distribution context. None of the entries below are SkillVetAI compatibility test results.
These checks parse the fixed package against dated platform rules. They do not execute the Skill or verify task behavior.
.claude/skills/sandbaseRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
.agents/skills/sandbaseRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
skills/sandbaseRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
This command is recorded from the source ecosystem and resolves the registry's latest release. The fixed release shown on this page should be inspected before adoption.
clawhub install @joeliu926/sandbaseclawhub inspect @joeliu926/sandbase --version 1.0.1This automated, non-executing scan is bound to this release hash. It is not a safety certification and may contain false positives or false negatives.
This is registry-supplied evidence for the recorded release, not an independent SkillVetAI scan. Check the canonical source for the full report, scanner versions, scope, and current moderation state.
The catalog stores hashes and an inventory summary for change detection. It does not republish the package contents.
sha256:fe174769491f75aabe117654ae0f591688e7b1b546697f7c51bc4e161f695b2bskill-card.mdSKILL.mdsandbase 1.0.1 - Revised the skill description and workflow to focus specifically on safe setup and connection of SandBase MCP in supported clients (Antigravity, Trae, Qoder, WorkBuddy, Pi). - Added strict, step-by-step procedures for verifying connection status, identifying supported clients, obtaining user confirmation before setup, running a single controlled CLI command, and securely registering the MCP bridge. - Expanded status vocabulary and emphasized reporting and evidence requirements for each connection stage. - Strengthened guidance on preventing exposure of secrets, avoiding inference or unauthorized changes, and treating CLI output as untrusted. - Removed skill-card.md from the project.