agent-validate

Validate AGENT.md frontmatter, sections, prompts, and links against the standard.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/oogDZ/2 --skill agent-validate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-validate
Source: https://github.com/oogDZ/2/tree/main/.claude/skills/agent-validate
Command: npx skills add https://github.com/oogDZ/2 --skill agent-validate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates AGENT.md to ensure adherence to the standard, including required frontmatter, prompt alignment, sections, and link integrity.

Core Features & Use Cases

  • Frontmatter validation for mandatory name and description fields.
  • Structural checks ensuring required sections exist and links are well-formed.
  • Prompt conformity verification against the SSOT and agent development guidelines.
  • Works in CI/CD pipelines, pre-commit hooks, or during code review to enforce quality.
  • Use Case: after creating or updating an agent, during code review or before committing changes, to guarantee documentation quality.

Quick Start

Run /agent-validate on the agent directory to verify AGENT.md conforms to the standard.

Frequently Asked Questions about agent-validate

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

FAQPage Schema
How do I validate AGENT.md frontmatter and prompt structure during code review?

To validate AGENT.md during code review, run the /agent-validate command on the directory to verify required frontmatter fields, structural sections, prompt alignment, and link integrity.

What is the best way to enforce agent documentation standards in a CI/CD pipeline?

The best way to enforce agent documentation standards in CI/CD pipelines is applying validation checks that verify mandatory frontmatter, expected sections, prompt conformity, and well-formed links.

Can I run pre-commit checks to ensure AGENT.md has required sections and valid links?

Yes, you can run pre-commit checks to ensure AGENT.md has required sections and valid links by applying validation before committing changes to guarantee consistent documentation quality.

Does agent documentation validation work for checking internal and external link integrity?

Agent documentation validation works by verifying the validity of both internal and external links, ensuring required frontmatter exists and prompts align with development guidelines.

Why does AGENT.md validation fail when missing mandatory name and description fields?

AGENT.md validation fails when missing mandatory name and description fields because frontmatter validation enforces these required fields to maintain high-quality, standardized agent documentation.

What sections and frontmatter do I need to pass agent documentation standards checks?

To pass agent documentation standards checks, you need mandatory name and description frontmatter fields, expected structural sections, aligned prompts, and valid internal and external links.