agentleFS
Sign inStart free
MSiccDevMSiccDev/ai-context-kit/skills/validate-agents-md/SKILL.md

validate-agents-md

Skill12 starsChanged 4 months agoMITView on GitHub

Validate AGENTS.md files for structural completeness, operational contract coverage, neutrality, and repository alignment.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 6 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when adding or updating root or nested AGENTS.md files.

    line 17
  2. Distinctive:

    Use this skill before accepting AGENTS policy changes.

    line 18
  3. Distinctive:

    Do not use this skill for user/project instruction validation.

    line 19
  4. Very specific:

    Run validation phases from references/phase-checks.md.

    line 27
  5. Very specific:

    Check for <!-- spec_version: ...

    line 28
  6. Distinctive:

    Keep the scoring rubric deterministic.

    line 49
  7. Distinctive:

    Avoid over-prescriptive style-only feedback.

    line 50
  8. Distinctive:

    Do not duplicate full normative specs when suggesting fixes.

    line 52

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Validate AGENTS.md

Purpose

Validate AGENTS.md files to ensure they are concise, operationally complete, and aligned with repository structure and governance.

When To Use

  • Use this skill when adding or updating root or nested AGENTS.md files.
  • Use this skill before accepting AGENTS policy changes.
  • Do not use this skill for user/project instruction validation.

Required Inputs

  • Target AGENTS.md path.
  • Repository path context for link/path validation.
  • Policy expectations for session-state and command namespace.

Workflow

  1. Run validation phases from references/phase-checks.md.
  2. Check for <!-- spec_version: ... --> comment: flag as WARNING if absent (pre-existing files may predate this requirement); flag as WARNING if present but older than 1.5.0.
  3. Generate report using references/report-contract.md.
  4. Apply deterministic scoring from references/scoring.md.
  5. Classify findings into critical/warning/enhancement buckets.
  6. Provide concrete fixes for operational contract gaps.

Output Expectations

  • Structured markdown report with five validation phases.
  • Compliance score and pass band.
  • Explicit list of critical issues, warnings, and enhancements.
  • Example fixes for common structural and policy failures.
  • Report schema follows references/report-contract.md.
  • Scoring and grade bands follow references/scoring.md.

Resources

  • Phase checks: references/phase-checks.md
  • Report contract: references/report-contract.md
  • Scoring model: references/scoring.md
  • Example target: ../../AGENTS.md

Constraints And Safety

  • Keep the scoring rubric deterministic; findings should be repository-specific and actionable.
  • Avoid over-prescriptive style-only feedback.
  • Preserve provider-neutral language.
  • Do not duplicate full normative specs when suggesting fixes.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free