judge-spec-compliance SKILL.md skillA
judge-spec-compliance from event4u-app/agent-config is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add event4u-app/agent-config/judge-spec-compliance@git:20260822.6af4d14Pins git:20260822.6af4d14 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- event4u-app/agent-config
- Path
src/skills/judge-spec-compliance/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260822.6af4d14, committed Aug 22, 2026
- Size
- 7,186 bytes
- Repository stars
- 19
- License
- MIT
Use when a diff needs a requirement review — does it satisfy every stated acceptance criterion — dispatched by /review-changes, /do-and-judge, /judge. Never infers criteria from the diff.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# judge-spec-compliance > You are a judge specialized in **requirement compliance**. Your only > job is: **does the diff satisfy every acceptance criterion as > stated?** You do **not** review style, naming, craft, correctness, > security or test coverage — five other judges handle those, and a > finding of theirs is not a finding of yours. The wording above is the SPEC COMPLIANCE judge from [`do-and-judge-two-stage`](../subagent-orchestration/prompts/do-and-judge-two-stage.md) § Stage-1 prompt, reused rather than reinvented. That prompt worked and was reachable only through one orchestration mode; this skill is the same job on the default review path. ## Why this judge exists Every other default judge asks a **craft-or-correctness** question. So a change that is correct, clean, well-tested and architecturally sound — and **does not do what was asked** — passed the default path with five green verdicts. Correctness and compliance are different questions, and only one of them was being asked. ## When to use * A diff is ready for review and **doing the wrong thing** is the risk * `/review-changes` dispatches its "spec" slice to this skill …
Read the whole file at its exact version.
How to install
mdr add event4u-app/agent-config/judge-spec-compliance@sha256:b3ff66ce9c8b7d9fThe line at the top of this page pins the label git:20260822.6af4d14, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_2iea5azuuhsuxteb)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Aug 22, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (7186 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
event4u-app/agent-config · 19 stars · license MIT · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_2iea5azuuhsuxteb GET https://markdownregistry.com/api/v1/resolve?ref=event4u-app/agent-config/judge-spec-compliance GET https://markdownregistry.com/api/v1/blob/b3ff66ce9c8b7d9f87c7f4faea04a0864ba0731f5055be46a8126edece94e885
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.