vitals

Run read-only diagnostic checks on a vibe-test plugin's references, templates, and state.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/estevanhernandez-stack-ed/vibe-test --skill vitals-estevanhernandez-stack-ed
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vitals
Source: https://github.com/estevanhernandez-stack-ed/vibe-test/tree/main/packages/vibe-test/skills/vitals
Command: npx skills add https://github.com/estevanhernandez-stack-ed/vibe-test --skill vitals-estevanhernandez-stack-ed

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Non-destructive diagnostics surface integrity issues across a vibe-test plugin by validating references, templates, and state prior to evolution.

Core Features & Use Cases

  • Seven read-only checks against plugin files, the unified profile, logs, and the anchored composition registry.
  • Banner-style report with per-check status and a concise summary for quick triage.
  • Non-destructive by design: no writes or remediation are performed; remediation is surfaced to the caller.
  • Useful as a pre-flight before /vibe-test:evolve or before publishing updates to ensure a clean baseline.

Quick Start

Run the vitals pre-flight to verify plugin integrity, references, and state before evolution proceeds.

Frequently Asked Questions about vitals

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run pre-flight validation checks on a vibe-test plugin?

Pre-flight validation is performed by running read-only diagnostic checks against the plugin's files, templates, logs, and state to surface integrity issues before code changes or generation. The process outputs a summary without performing writes.

What does a structural health check for plugin integrity include?

A structural health check includes seven read-only checks that validate SKILL references, templates, builder profiles, logs, and the anchored composition registry to identify integrity issues across a vibe-test plugin.

Can I use diagnostic reporting to check plugin state without modifying files?

Yes, the diagnostic reporting is non-destructive by design and guarantees no writes or remediation are performed. It operates strictly against read-only paths and surfaces remediation steps to the caller.

When do I need to run plugin diagnostics and integrity validation?

You need to run plugin diagnostics before executing evolution procedures or publishing updates. Validating references and state beforehand ensures a clean baseline and prevents integrity issues from propagating.

What is the best way to triage integrity issues found in plugin logs and templates?

The best way to triage integrity issues is to review a banner-style report that provides per-check status outcomes (pass, warn, fail) alongside a concise summary, allowing you to quickly identify and address problems.