vc-audit-vc

Validate agent harness consistency across Claude, Codex, README.md, and protocol files.

Updated Jun 20, 2026
One-click install
npx skills add https://github.com/tutran27/trust-room-AI --skill vc-audit-vc-tutran27
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vc-audit-vc
Source: https://github.com/tutran27/trust-room-AI/tree/main/.agents/skills/vc-audit-vc
Command: npx skills add https://github.com/tutran27/trust-room-AI --skill vc-audit-vc-tutran27

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires node, and includes scripts (resource) components.

What problem does it solve?

This skill addresses the need for verifying the consistency and synchronization of the agent harness layer across Claude, Codex, README.md, and protocol files. It helps identify discrepancies, mismatches, or drifts when agents, skills, documentation, or development-protocol files are modified.

Core Features & Use Cases

  • Agent Parity: Validates the parity between Claude and Codex agent definitions.
  • Skill Audit: Checks the consistency of skill definitions and references in the skill registry.
  • README.md Sync: Ensures that the README.md is up-to-date with the latest agent, skill, and protocol changes.
  • Protocol Wiring: Validates the correct wiring of protocol files in the agent and skill definitions.
  • Seed/Scaffold Consistency: Checks the consistency of seed/scaffold files for potential changes.
  • Kit Portability: Validates the portability of the kit across different environments.
  • Skill Invocation Wiring: Ensures that all skill invocations in agents are correctly wired and registered.

Quick Start

Run the skill with the command: node .claude/skills/vc-audit-vc/scripts/validate-agent-parity.mjs

Frequently Asked Questions about vc-audit-vc

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

FAQPage Schema
How do I validate agent parity between Claude and Codex definitions?

Agent parity validation checks consistency between Claude and Codex agent definitions using a Node script that compares file structures and flags mismatches caused by recent modifications.

What is the best way to keep README.md synchronized with protocol and skill changes?

README.md synchronization verifies that your documentation reflects the latest agent, skill, and protocol file modifications. The audit script scans for documentation drift and identifies outdated references across the harness.

How does protocol wiring validation work for agent and skill definitions?

Protocol wiring validation verifies that protocol files referenced within agent and skill definitions are correctly connected, ensuring all skill invocations are properly wired and registered to prevent broken execution paths.

Do I need Node installed to run agent harness consistency checks?

Yes, Node is a required dependency for running agent harness consistency checks. The validation scripts rely on Node's file processing and comparison utilities to evaluate seed/scaffold files and kit portability across different environments.

Why does my skill registry audit show mismatches after modifying agent files?

Skill registry audits reveal mismatches when skill definitions or references are modified without updating the registry. The audit identifies discrepancies in the registry consistency, protocol wiring, and seed/scaffold files to highlight configuration drift.

Can I check seed and scaffold file consistency across different environments?

Yes, you can check seed and scaffold file consistency across environments. The audit validates kit portability by comparing these foundational files to detect potential changes or drift when the harness layer is moved or updated.