vibe-skill-audit

Audit SKILL.md files for Vibe standards compliance and drift.

6|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/jacobcy/vibe-coding-control-center --skill vibe-skill-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vibe-skill-audit
Source: https://github.com/jacobcy/vibe-coding-control-center/tree/main/skills/vibe-skill-audit
Command: npx skills add https://github.com/jacobcy/vibe-coding-control-center --skill vibe-skill-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill enforces repository-local governance for Vibe-native skills by validating SKILL.md content against project standards, preventing semantic drift, and ensuring shell and shared-state boundaries are respected.

Core Features & Use Cases

  • Standards alignment: Checks that skills cite the correct docs/standards files and prefers direct references over duplicated prose.
  • Command reality checks: Runs repository helpers to verify bin/vibe domains, subcommands, and options actually exist and flags capability gaps.
  • Drift detection and classification: Compares file timestamps, detects newer standards, and classifies findings as Blocking, Missing Reference, Capability Gap, or Drift Warning.
  • Use case: When creating or updating a skills/vibe-* SKILL.md, run this audit to align wording, fix outdated commands, and capture required references.

Quick Start

Run the audit script on a target SKILL.md and fix any Blocking, Missing Reference, Capability Gap, or Drift Warning entries reported.

Frequently Asked Questions about vibe-skill-audit

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

FAQPage Schema
How do I audit SKILL.md files for standards compliance and drift?

Audit SKILL.md files for standards compliance by running the audit script to validate references, verify bin/vibe command presence, compare file timestamps for drift, and classify findings as Blocking, Missing Reference, Capability Gap, or Drift Warning.

What is semantic drift detection in repository skill definitions?

Semantic drift detection in repository skill definitions compares file timestamps to identify newer standards, checking that skills cite correct docs/standards files and flagging outdated wording or duplicated prose for correction during review workflows.

How do I verify bin/vibe subcommands and options actually exist in a repository?

Verify bin/vibe subcommands and options by running repository helpers through the audit script, which checks command reality and flags any capability gaps where documented commands do not actually exist in the repository.

Can I use skill audits during creation and update workflows for vibe-native skills?

Yes, you can use skill audits during creation and update workflows for skills/vibe-* definitions to align wording, fix outdated commands, capture required references, and ensure shell and shared-state boundaries are respected before changes are finalized.

Why does my SKILL.md audit report a Missing Reference classification?

A SKILL.md audit reports a Missing Reference classification when the skill definition does not cite the correct docs/standards files, indicating that direct references are absent or replaced by duplicated prose instead of proper citations.

What are the limitations of vibe skill audits for drift detection?

Vibe skill audits are limited to repo-local skills/vibe-* definitions and SKILL.md files, relying on file timestamp comparisons and repository helper availability to detect drift, classify findings, and validate standards compliance.