Validate agents md
AI Context Kit provides a structured, instruction-based framework for context-aware AI collaboration across LLM providers. It includes authoritative specs, canonical templates, and skills workflows for creating and validating user context and project AGENTS.md files.
npx -y skills add MSiccDev/ai-context-kit --skill validate-agents-mdAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 11 stars11 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Validate AGENTS.md files for structural completeness, operational contract coverage, neutrality, and repository alignment.
SKILL.md
2.5 KB, as published. Nobody here has run it
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.mdfiles. - Use this skill before accepting AGENTS policy changes.
- Do not use this skill for user/project instruction validation.
How to Invoke
Load or attach this file's contents into your AI session to activate the workflow (paste, upload, or reference with #file:skills/validate-agents-md/SKILL.md in VS Code Copilot Chat). In Claude Projects, add it to project knowledge. See Invoking Skills in the README for full platform guidance.
Required Inputs
- Target
AGENTS.mdpath. - Repository path context for link/path validation.
- Policy expectations for session-state and command namespace.
Workflow
- Run validation phases from
references/phase-checks.md. - Check for
<!-- spec_version: ... -->comment: flag as WARNING if absent (pre-existing files may predate this requirement); flag as WARNING if present but older than1.4.3. - Generate report using
references/report-contract.md. - Apply deterministic scoring from
references/scoring.md. - Classify findings into critical/warning/enhancement buckets.
- 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.