validate-agent-files

You can validate agent files by checking YAML frontmatter for required name and description fields in SKILL.md. This validation catches missing frontmatter, wrong naming conventions, and invalid body content across provider folders during pre-commit checks.

The correct format requires YAML frontmatter containing name and description properties, proper file naming conventions, and non-empty body content. Validation applies to agent, skill, prompt, and instruction files across multiple provider folders.

Yes, cross-provider validation supports customization files in .github, .claude, .codex, and .config/opencode folders. It detects misconfigurations in file types, naming conventions, and frontmatter structure across these provider directories.

The best way to catch missing frontmatter is running validation audits during code reviews. This enforces YAML frontmatter presence of name and description for SKILL.md and provides guidelines to fix issues before committing changes.

Prompt file validation fails when files have missing frontmatter, incorrect naming conventions, or empty bodies. The validator checks for required YAML frontmatter fields and enforces non-empty content across all agent, skill, and instruction files.

No dependencies are required to validate agent files and instructions. The validation works directly on provider folders to check YAML frontmatter, file types, naming conventions, and body content without external packages.