vibesafe

Data Community v0.2.0-pre1

Skill notes

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).

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
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)
Author source file SKILL.md

# 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).

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.