loop-verifier

Verifies loop triage reports against rubric checks for cache citations and L1 compliance.

Updated Jun 17, 2026
One-click install
npx skills add https://github.com/ndestates/ndestates-website --skill loop-verifier-ndestates
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: loop-verifier
Source: https://github.com/ndestates/ndestates-website/tree/main/.copilot/skills/loop-verifier
Command: npx skills add https://github.com/ndestates/ndestates-website --skill loop-verifier-ndestates

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It provides an independent checker for loop triage outputs, ensuring reports follow the maker/checker split by validating artifacts against a fixed rubric instead of trusting the maker's reasoning. ## Core Features & Use Cases - Rubric-Based Validation: Checks cache citations, L1 no-auto-fix compliance, STATE.md synchronization, run log entries, brevity, and token discipline. - Fail-Closed Enforcement: Blocks loop completion in STATE.md when any critical check fails and lists required fixes for the maker to re-run triage. - Use Case: After a loop-triage run produces a report under reports/loops/, invoke this verifier with the report path to confirm the artifact cites the cache manifest, stays within the L1 budget, and updated STATE.md and the run log consistently. ## Quick Start Verify the latest triage report in reports/loops/ against the loop rubric and tell me whether it passes or fails.

Frequently Asked Questions about loop-verifier

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

FAQPage Schema
How do I verify a loop triage report?▼

Pass the path to the report under reports/loops/ as the argument, or let the verifier pick the latest report by date. It checks the artifact against the rubric and returns a PASS or FAIL verdict with per-check notes.

What checks does the loop verification rubric include?▼

The rubric covers cache citation with manifest plus at least two cache paths, L1 compliance with no auto-fix or source exploration, STATE.md synchronization, run log row presence, executive summary brevity under 120 words, and token discipline.

Does the verifier re-read the codebase to confirm findings?▼

No, the verifier judges only the report artifact and its supporting state files. It explicitly does not re-read source code, accepting or rejecting cache miss claims based on whether they are documented.

What happens when a loop verification fails?▼

The verifier outputs a numbered list of required fixes and does not mark the loop complete in STATE.md. The maker must re-run triage to address the failures before verification can pass.

When should I run the loop verifier in the workflow?▼

Run it after loop-triage produces a report. It acts as the independent checker in the maker/checker split, confirming the artifact meets budget and compliance rules before the loop is closed.