vc:audit-vc

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

Updated May 10, 2026
One-click install
npx skills add https://github.com/cryborg1211/quant_trading_telegram_bot --skill vc-audit-vc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vc:audit-vc
Source: https://github.com/cryborg1211/quant_trading_telegram_bot/tree/main/.agents/skills/vc-audit-vc
Command: npx skills add https://github.com/cryborg1211/quant_trading_telegram_bot --skill vc-audit-vc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

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

Core Features & Use Cases

  • Parity validation across Claude and Codex agent definitions.
  • Discovery and synchronization checks for skills and README documentation.
  • Protocol wiring and seed-file consistency audits to maintain a coherent development surface.
  • Quick troubleshooting guidance when mismatches are found, including targeted patching guidance.

Quick Start

Run the Claude parity validator, the shared skill discovery validator, the README.md sync validator, the protocol wiring validator, the seed consistency validator, and the kit portability validator from the skill root.

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 parity between Claude and Codex agent definitions?

To validate parity between Claude and Codex agent definitions, run dedicated validator scripts from the skill root that execute parity validation checks across the agent harness to ensure internal consistency and correct wiring.

What is README sync validation and how does it work for skills?

README sync validation checks synchronization between skills and README documentation by running dedicated validator scripts that discover mismatches when files move, split, or drift across the development surface.

How do I audit protocol wiring and seed file consistency?

To audit protocol wiring and seed file consistency, execute the protocol wiring validator and seed consistency validator scripts from the skill root to maintain coherent development protocol files.

Why does my agent harness have internal consistency issues after files split or move?

Agent harness internal consistency issues occur when agents, skills, README.md, or development-protocol files move, split, or drift across Claude and Codex definitions, requiring parity validation and protocol wiring audits to detect and patch mismatches.

Can I use script-based validators to check agent harness portability?

Yes, you can run the kit portability validator and seed consistency validator scripts from the skill root to validate portability and ensure correct wiring across Claude, Codex, README.md, and protocol files.

What's the best way to troubleshoot development protocol mismatches across agents?

The best way to troubleshoot development protocol mismatches is running validator scripts that check Claude and Codex parity, skill discovery, README sync, and protocol wiring, then applying targeted patching guidance provided when mismatches are found.