vc-audit-vc

Audit VC harness health across Claude/Codex parity and protocol wiring.

1.1k|223|Updated May 27, 2026
One-click install
npx skills add https://github.com/withkynam/vibecode-pro-max-kit --skill vc-audit-vc-withkynam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vc-audit-vc
Source: https://github.com/withkynam/vibecode-pro-max-kit/tree/main/.claude/skills/vc-audit-vc
Command: npx skills add https://github.com/withkynam/vibecode-pro-max-kit --skill vc-audit-vc-withkynam

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Audit the VC harness health across Claude/Codex parity, skill registry consistency, README.md sync, and protocol wiring. Use when agents, skills, README.md, or development-protocol files move, split, or drift.

Core Features & Use Cases

  • Parity validators for Claude vs Codex agent parity
  • Skill registry and guide-sync validators
  • Protocol wiring and seed consistency checks
  • Kit portability and skill-invocation wiring validators
  • Agent frontmatter and READMEs synchronization checks

Quick Start

Run the provided validators located in .claude/skills/vc-audit-vc/scripts to verify parity, discovery, guide sync, protocol wiring, seeds, portability, and invocation wiring.

Frequently Asked Questions about vc-audit-vc

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

FAQPage Schema
How do I check Claude and Codex agent parity in my development harness?

To check Claude and Codex agent parity, run the parity validators located in the skill scripts directory. These validators audit agent configurations to verify behavioral alignment and detect configuration drift across the harness.

What is skill registry consistency validation?

Skill registry consistency validation is the process of verifying that registered skills match their actual definitions and documentation. It ensures discovery mechanisms correctly map to available skills without missing or broken references.

How do I keep README.md synchronized with development protocol files?

To keep README.md synchronized with development protocols, execute the guide-sync and README synchronization validators. They detect drift between documentation and protocol wiring, ensuring agent guides match the actual harness configuration.

Can I use these validators to check skill-invocation wiring and kit portability?

Yes, you can use these validators to check skill-invocation wiring and kit portability. The scripts include dedicated checks that verify invocation paths are correctly wired and the kit remains portable across different environments.

When should I run a harness health audit for agents and skills?

You should run a harness health audit when agents, skills, README.md, or development-protocol files move, split, or drift. It verifies seed consistency, frontmatter synchronization, and protocol wiring to prevent integration failures.