agents-validator

Validate CLAUDE.md and AGENTS.md structural and content requirements in project directories.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Users setting up agent teams frequently encounter broken workflows due to misconfigured CLAUDE.md and AGENTS.md files, leading to wasted time debugging setup issues instead of building features.

Core Features & Use Cases

  • Structural Validation: Ensures every CLAUDE.md contains only the standalone @AGENTS.md import line with no extra content.
  • Content Standard Checks: Verifies AGENTS.md files meet minimum word count requirements (200-300 words for root, 80-150 for modules) and have valid Markdown headings.
  • Hierarchical Scanning: Supports auditing root-only, root+modules, or full nested directory structures with custom ignore patterns.
  • Use Case: A developer preparing a multi-module project for agent teams can run this validation to catch missing imports, underdeveloped AGENTS.md files, and orphaned AGENTS.md entries before launching their workflow.

Quick Start

Use the agents-validator skill to audit the CLAUDE.md and AGENTS.md structure in your current project directory.

Frequently Asked Questions about agents-validator

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

FAQPage Schema
How do I validate CLAUDE.md and AGENTS.md file structures for agent workflows?

Validating CLAUDE.md and AGENTS.md file structures requires checking that CLAUDE.md contains only the standalone @AGENTS.md import line and verifying AGENTS.md files meet minimum word count thresholds. The agents-validator scans project directories to enforce these structural rules automatically.

What are the content requirements for AGENTS.md files in nested project directories?

AGENTS.md content requirements mandate 200-300 words for root-level files and 80-150 words for module-level files, plus valid Markdown headings. The validator audits root-only, root+modules, or full nested directory structures to ensure compliance across the hierarchy.

Why does my agent team workflow break due to misconfigured CLAUDE.md files?

Agent team workflows break when CLAUDE.md files contain extra content beyond the standalone @AGENTS.md import line. Running a structural validation audit catches missing imports, underdeveloped AGENTS.md files, and orphaned entries before launching the workflow.

Can I ignore certain directories when auditing AGENTS.md file hierarchies?

You can ignore specific directories when auditing AGENTS.md file hierarchies by applying configurable ignore patterns. The validator supports custom ignore rules to skip irrelevant paths during root, module, or nested directory scans.

How do I audit a multi-module project for agent team setup before deployment?

Auditing a multi-module project for agent team setup involves scanning the directory structure to detect missing imports and underdeveloped AGENTS.md files. The validator outputs standardized pass, warn, or fail reports to resolve pre-deployment configuration issues.

What is the best way to check if AGENTS.md files meet minimum word count thresholds?

Checking AGENTS.md minimum word count thresholds is best handled by an automated validation audit that verifies 200-300 words at root and 80-150 words at module levels. The scan produces standardized audit reports flagging any files that fall short.