config-validator

Validate internal references and file existence in the .agent directory.

3|1|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/Harmitx7/tribunal-kit --skill config-validator-harmitx7
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: config-validator
Source: https://github.com/Harmitx7/tribunal-kit/tree/main/.agent/skills/config-validator
Command: npx skills add https://github.com/Harmitx7/tribunal-kit --skill config-validator-harmitx7

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents unpredictable agent behavior by verifying that all internal references between agents, skills, workflows, and scripts are valid and consistent within the .agent/ directory.

Core Features & Use Cases

  • System Integrity Check: Validates that all declared agents, skills, workflows, and scripts exist on the filesystem.
  • Reference Consistency: Ensures that references in agent frontmatter and routing tables correctly point to existing files.
  • Orphan File Detection: Identifies files that exist but are not referenced by any part of the system.
  • Use Case: After adding a new agent or modifying routing rules, run this skill to catch any broken links before they cause runtime errors or unexpected agent behavior.

Quick Start

Run the config-validator skill to check the integrity of the agent system configuration.

Frequently Asked Questions about config-validator

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

FAQPage Schema
How do I check agent system configuration consistency and prevent runtime errors?

To check agent system configuration consistency, you validate the `.agent` directory by cross-referencing agent frontmatter and routing tables against the filesystem to catch missing files and broken links.

Why does my agent system behave unpredictably after modifying routing rules?

Agent systems behave unpredictably after modifying routing rules because broken internal references to agents, skills, or scripts exist. Validating reference consistency detects these configuration integrity issues before runtime.

What is the best way to find orphan files in an agent system configuration?

The best way to find orphan files in an agent system configuration is to run an integrity check that cross-references the filesystem with routing tables, identifying any existing files that are not referenced.

Does agent frontmatter validation detect missing scripts before deployment?

Yes, agent frontmatter validation detects missing scripts by verifying that all declared agents, skills, workflows, and scripts exist on the filesystem and are correctly referenced before deployment.

Can I use automated configuration validation for a large agent directory?

You can use automated configuration validation for a large agent directory to systematically cross-reference routing tables and frontmatter, ensuring system integrity and preventing broken links at scale.

When should I run an agent system integrity check on my workflow configuration?

You should run an agent system integrity check on your workflow configuration immediately after adding a new agent or modifying routing rules to catch broken links before they cause unexpected behavior.