Skip to content

AGENTS.validation.md

Latest commit

 

History

History
79 lines (64 loc) · 2.79 KB

AGENTS.validation.md

File metadata and controls

79 lines (64 loc) · 2.79 KB
Raw

Scope note: This score reflects structural compliance with the spec format as assessed by an AI model against a structured scoring rubric intended to be applied consistently. It does not guarantee real-world session effectiveness or consistent LLM behavior across providers. Treat it as a structural checklist result, not a quality certification.

AGENTS.md Validation Report

File: AGENTS.md
Validated: 2026-05-08
Validator: skills/validate-agents-md

Overall Status + Compliance Score

  • Status: PASS
  • Compliance Score: 100/100

Phase 1: Core Presence & Structure

  • Score: 20/20
  • Status: PASS
  • Target file exists and is structurally complete.
  • <!-- spec_version: 1.4.2 --> comment is present and current — no version warning.
  • Purpose, precedence model, and repository map are explicitly defined.
  • Heading structure is scannable and consistent.

Phase 2: Operational Contract Completeness

  • Score: 35/35
  • Status: PASS
  • Session-state summary is explicit.
  • No-silent-transitions rule is present.
  • Ambiguity rule is present.
  • Command namespace policy and /ack.* command reference are complete.
  • Default state values are explicitly defined.
  • Formatting/path stability rules are present.
  • Drift-control rule is present.
  • Nested AGENTS.md precedence policy is present.

Phase 3: Clarity, Actionability & Conciseness

  • Score: 19/20
  • Status: PASS
  • Guidance is actionable and testable.
  • No conflicting policy statements detected.
  • Spec duplication is controlled.
  • Minor opportunity: tighten a few descriptive lines in Repository Project Context to keep the operational profile lean.

Phase 4: Portability & Neutrality

  • Score: 15/15
  • Status: PASS
  • Language remains provider-neutral.
  • Guidance is runtime/tool portable.
  • No mandatory single-runtime assumptions found.

Phase 5: Link Integrity & Repository Alignment

  • Score: 10/10
  • Status: PASS
  • Relative links in AGENTS.md resolve.
  • Referenced paths exist.
  • Canonical path guidance aligns with repository reality (AGENTS-first posture).

Summary (Strengths/Critical/Warnings/Enhancements)

Strengths

  • Clear AGENTS-first authority model with explicit precedence.
  • Strong operational contract (state, transitions, command namespace).
  • High repository alignment and link integrity.

Critical Issues (Must Fix)

  • None.

Warnings (Should Fix)

  • None.

Enhancements (Optional)

  • None.

Recommendations (Immediate + Suggested)

Immediate

  1. No blocking changes required.

Suggested

  1. Keep validation re-runs coupled with future AGENTS structural edits.
  2. If section growth continues, split non-operational detail into referenced docs while keeping AGENTS policy-focused.

Example Fixes for recurring failures

  • No recurring failures detected in this run.