mcpbeat Sign in

Vibeguard Agent Skill

Lightweight anti-hallucination workflow for task kickoff, review prioritization, and regression retrospectives. Use when the user asks for guardrails, task contracts, risk scoring, or review templates.

2k tokens
context cost
the whole folder, loaded on every use
4
files
instructions only
0
copies elsewhere
how many repositories repackaged it
242
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/majiayu000/spellbook --skill vibeguard

The instruction itself

11 sections, as written by the author

VibeGuard

Lightweight VibeGuard for everyday use inside Spellbook.

This skill helps with three moments where AI-assisted work usually drifts:

  • before implementation starts
  • while review findings are being prioritized
  • after regressions or avoidable mistakes happen

What This Skill Includes

  • A task contract checklist for scoping work before coding
  • A scoring matrix for prioritizing findings with evidence
  • A weekly review template for regression and guardrail retrospectives

Hard Boundaries

This skill is intentionally lightweight.

It does:

  • guide task kickoff
  • structure review output
  • make risk tradeoffs explicit

It does not:

  • install hooks
  • run guard scripts automatically
  • patch global Claude or Codex configuration
  • claim that full VibeGuard enforcement is active

If the user asks for automated interception, repo-level rules, or environment setup, escalate to the full VibeGuard repository and tooling.

When To Use It

Trigger this skill when the user asks for:

  • anti-hallucination guardrails
  • task startup checks
  • review scoring or triage
  • regression prevention
  • retrospective templates
  • "vibeguard" by name

Workflow

1. Start With The Task Contract

Open references/task-contract.yaml and confirm:

  • goal
  • source of truth
  • acceptance criteria
  • scope

Do not move into implementation until these are concrete.

2. Score Findings Before Acting

Open references/scoring-matrix.md and score each finding on:

  • impact
  • effort
  • risk
  • confidence

Use the score to separate urgent fixes from weak guesses.

3. Pick The Right Delivery Mode

  • 1-2 files: implement directly once the contract is clear
  • 3-5 files: write a short spec or step plan first
  • 6+ files: produce a full design/spec and staged execution plan

4. Review The Failure, Not Just The Symptom

If something regressed, identify which defense failed:

  • scope control
  • source-of-truth validation
  • verification depth
  • review prioritization
  • missing guardrail

Then capture the follow-up in references/review-template.md.

Expected Outputs

Depending on the request, produce one of these:

  • a filled task contract
  • a scored findings table with priorities
  • a short regression review or weekly retrospective

Reference Files

  • references/task-contract.yaml - kickoff checklist
  • references/scoring-matrix.md - prioritization model
  • references/review-template.md - retrospective template

Other skills for the same job

different authors, same section of the catalogue
Workflow Patterns
by ComeOnOliver
×2

Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.

6k tokens
Iso Standards Readiness
by K-Dense-AI
×1

Prepares and structurally reviews readiness evidence for ISO management-system and laboratory-competence standards - ISO 13485 medical device QMS, ISO 14971 device risk management, ISO/IEC 17025 testing and calibration laboratories, and ISO 15189 medical laboratories. Use when organizing declared scope, controlled documents, risk-management files, scope of accreditation, traceability, CAPA, external-provider controls, or bounded local evidence manifests, and when separating ISO certification from laboratory accreditation, FDA QMSR inspection, CLIA certification, MDSAP, and EU MDR/IVDR evidence boundaries. Not for legal applicability, compliance, certification, or accreditation decisions; contains no clause text.

67k tokens scripts
Statistical Power
by K-Dense-AI
×1

Sample-size and statistical power calculations for planning studies. Use whenever someone asks "how many subjects/samples/replicates do I need", wants an a priori power analysis, a minimum detectable effect (MDE), a power curve, or needs to justify a sample size for a grant, IRB protocol, or pre-registration. Covers closed-form power for t-tests, ANOVA, proportions, correlations, chi-square, and regression, plus simulation-based (Monte Carlo) power for designs with no formula — logistic/Poisson regression, mixed models, cluster-randomized trials, survival, and interactions. Use this skill even when the request only mentions an effect size, alpha, or "80% power" without saying "power analysis" explicitly. For laying out the study (randomization, blocking, factorial/DOE, crossover, sequential designs) use experimental-design; for analyzing data already collected and reporting it use statistical-analysis.

13k tokens scripts
General Figure Guide
by BioTender-max
×1

Universal QA checklist for generated scientific plots: overlapping labels, clipped text, missing axes/legends, overcrowded data, and cross-journal resolution/format guidance.

2k tokens
Nerdzao Elite
by ComeOnOliver
×1

Senior Elite Software Engineer (15+) and Senior Product Designer. Full workflow with planning, architecture, TDD, clean code, and pixel-perfect UX validation.

3k tokens
Pinchbench
by ComeOnOliver
×1

Run PinchBench benchmarks to evaluate OpenClaw agent performance across real-world tasks. Use when testing model capabilities, comparing models, submitting benchmark results to the leaderboard, or checking how well your OpenClaw setup handles calendar, email, research, coding, and multi-step workflows.

2096k tokens scripts
Workflow Patterns
by ComeOnOliver
×1

Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.

6k tokens
Powertoys Verification
by microsoft
vendor

Verify PowerToys behavior end-to-end with the winapp CLI across two scenarios: (A) a module's release checklist against the installed build; (B) PR validation — derive each PR's checklist from its description + diff, then drive it against the installed build (a merged/shipped PR, or a whole release/hotfix set) or by building + sideloading the module when the PR isn't in the build yet (unmerged or not-yet-released). Drive each item via UIA invoke / Named Events / settings.json edits / clipboard / GPO / SendInput, and emit a structured PASS / FAIL / BLOCKED verdict per item with evidence (FAIL distinguishes product defects from stale/ambiguous checklist items). Use when asked to verify a module checklist, validate a PR, sign off a release/hotfix's PRs, or QA installed/sideloaded PowerToys bits. Combines generic winapp ui mechanics (references/winapp-ui-testing.md) with PT-specific recipes, per-scenario playbooks (references/scenarios/), and the helper .ps1 files shipped with this skill.

86k tokens scripts

How to use it

Copy the folder

Take majiayu000/vibeguard from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.