vibesafe
- Repo stars 330
- License MIT
- Author repo claude-skill-registry
- Domain
- Data
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 100 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @majiayu000 · v0.2.0-pre1 · MIT
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No explicit requirements detected
- Detected file/system behavior
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- None (reference only)
# Vibesafe MCP Skill
Provides full control of the Vibesafe toolchain through the MCP server exposed by this plugin.
## When to Use
- User asks to run `vibesafe scan`, `compile`, `test`, `save`, `diff`, or `status`.
- Need to regenerate implementations from specs or check drift against checkpoints.
- Want to query registry contents, provider config, or checkpoints via the MCP tools.
## Available Tools
- `scan` — list all registered Vibesafe units with metadata.
- `compile` — generate implementations for a unit (supports `target`, `force`).
- `test` — run doctests/quality gates (optional `target`).
- `save` — activate checkpoints (optional `target`).
- `status` — report version, unit counts, environment.
## Examples
- “List all vibesafe units” → use `scan`.
- “Recompile app.math.ops/fibonacci” → call `compile` with `target`.
- “Run vibesafe tests” → call `test`.
- “Save checkpoints for all units” → call `save`.
- “Check drift” → call `diff` (via status+diff as available).
Sections and files
Listed in source order.
sections -> When to Use → Available Tools → Examples
terms -> Provides full control of the Vibesafe toolchain through the MCP server exposed by this plugin.
files/cmd -> vibesafe scan · compile · test · save · diff · status · scan · target
body sha256 -> 85e70690de43
When to Use
User asks to run
vibesafe scan,compile,test,save,diff, orstatus. Need to regenerate implementations from specs or check drift against checkpoints. Want to query registry contents, provider config, or checkpoints via the MCP tools.Available Tools
scan— list all registered Vibesafe units with metadata.compile— generate implementations for a unit (supportstarget,force).test— run doctests/quality gates (optionaltarget).save— activate checkpoints (optionaltarget).status— report version, unit counts, environment.Examples
“List all vibesafe units” → use
scan. “Recompile app.math.ops/fibonacci” → callcompilewithtarget. “Run vibesafe tests” → calltest. “Save checkpoints for all units” → callsave. “Check drift” → calldiff(via status+diff as available).