vibesafe
- Repo stars 330
- License MIT
- Author updated Live
- Author repo claude-skill-registry
- Domain
- Data · vibesafe · codegen · mcp
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 100 / 100 · audit passed
- 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 special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
---
name: vibesafe
description: Uses the Vibesafe MCP server to scan, compile, test, save, diff, and report status for Vibesafe…
category: data
runtime: no special runtime
---
# vibesafe output preview
## PART A: Task fit
- Use case: Uses the Vibesafe MCP server to scan, compile, test, save, diff, and report status for Vibesafe units. Activate when the user asks to run vibesafe CLI commands (scan/compile/test/save/diff/status), regenerate code from specs, or inspect drift/checkpoints..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “When to Use / Available Tools / Examples” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Uses the Vibesafe MCP server to scan, compile, test, save, diff, and report status for Vibesafe units. Activate when the user asks to run vibesafe CLI commands (scan/compile/test/save/diff/status), regenerate code from specs, or inspect drift/checkpoints.”.
- **02** When the source has headings, the agent prioritizes “When to Use / Available Tools / Examples” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Validate with a small run
Start with a small task and check whether the result follows “When to Use / Available Tools / Examples”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: vibesafe
description: Uses the Vibesafe MCP server to scan, compile, test, save, diff, and report status for Vibesafe…
category: data
source: majiayu000/claude-skill-registry
---
# vibesafe
## When to use
- Uses the Vibesafe MCP server to scan, compile, test, save, diff, and report status for Vibesafe units. Activate when t…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “When to Use / Available Tools / Examples” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "vibesafe" {
input -> user goal + target files + boundaries + acceptance criteria
context -> When to Use / Available Tools / Examples
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}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, 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” → call
compilewithtarget. - “Run vibesafe tests” → call
test. - “Save checkpoints for all units” → call
save. - “Check drift” → call
diff(via status+diff as available).
Decide Fit First
Design Intent
How To Use It
Boundaries And Review