agentsclimarketplace

Validate project instructions

Skill MSiccDev/ai-context-kit/skills/validate-project-instructions

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.

Install
npx -y skills add MSiccDev/ai-context-kit --skill validate-project-instructions

Assembled 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 project-context AGENTS.md files for required sections, session-state model completeness, role quality, and scoring compliance.

SKILL.md

2.5 KB, as published. Nobody here has run it

Validate Project Context AGENTS

Purpose

Validate project-context AGENTS.md files with structured checks for required sections, session-state controls, role definitions, and core required-section completeness based on a deterministic scoring rubric.

When To Use

  • Use this skill to validate project-context AGENTS.md files.
  • Use this skill when reviewing project context quality prior to active use.
  • Do not use this skill for user-context 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-project-instructions/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 project-context AGENTS.md path.
  • Expected section model and command reference expectations.
  • Any strictness preferences for warnings vs required fixes.

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.4.3.
  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. Produce project-specific remediation guidance.

Output Expectations

  • Structured markdown report with five validation phases.
  • Clear status for critical issues vs warnings.
  • Numeric score and grading band.
  • Concrete example fixes for major gaps.
  • 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 findings specific and actionable.
  • Preserve project terminology when proposing fixes.
  • Keep validation language provider-neutral.
  • Do not rewrite source files automatically.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.