conformance-debug SKILL.md skillA
conformance-debug from uze-sh/uze is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add uze-sh/uze/conformance-debug@git:20261017.1d0b3a6Pins git:20261017.1d0b3a6 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- uze-sh/uze
- Path
.agents/skills/conformance-debug/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261017.1d0b3a6, committed Oct 17, 2026
- First version recorded
- Aug 29, 2026
- Size
- 18,148 bytes
- Repository stars
- 3
- License
- Apache-2.0
Fast, targeted debugging of the Harness Conformance Lab (conformance/) — use whenever a conformance check fails (locally or in CI), a check is recorded as a declared limitation, a harness version drifted, a harness TUI check needs poking at directly, or you're about to guess at a fix instead of reproducing the real failure. Covers reading the failure's shape, checking the vendor's current docs/changelog/issues before touching code, the --sandbox and --experiment fast loops, proving the…
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
# Debugging the Harness Conformance Lab The Lab runs the real vendor CLI (Claude Code, Codex, OpenCode, Antigravity) against a synthetic provider in a disposable Docker container. What every harness must prove lives in `conformance/contract/` (outcome terms, no vendor named); how each harness is driven lives in `conformance/harnesses/<vendor>/bindings.py`; what is genuinely unique to a vendor stays in its `scenarios.py`. A full gate run (`python3 conformance/lab.py --harness <h>`) takes 6-11 minutes and only tells you pass/fail per check. **Never iterate against that loop.** There are seconds-long loops built for exactly this — reach for them first. The Lab's whole value is that a green is real. Two things make a green false, and both have shipped for months before: a check that passes because nothing happened (a hook that never ran, a tool call the harness rejected before executing), and a provider that speaks a wire shape the real API does not, so the harness silently does something else than it would in production. Every step below exists to catch one of those. ## Step 0 — is the world still the one the Lab assumes? …
Read the whole file at its exact version.
How to install
mdr add uze-sh/uze/conformance-debug@sha256:a5d88edd3c21c64bThe line at the top of this page pins the label git:20261017.1d0b3a6, 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_olku4oiliow26n5v)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Aug 29, 2026 and Oct 17, 2026, about one every 16 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261017.1d0b3a6 latest | 2026-10-17 | 1d0b3a6 | 18,148 B | A | view · diff |
| git:20261007.3aa314d | 2026-10-07 | 3aa314d | 18,143 B | A | view · diff |
| git:20260902.38a0fa1 | 2026-09-02 | 38a0fa1 | 15,140 B | A | view · diff |
| git:20260829.d2a93b0 | 2026-08-29 | d2a93b0 | 5,560 B | A | view |
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 (18148 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
uze-sh/uze · 3 stars · license Apache-2.0 · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_olku4oiliow26n5v GET https://markdownregistry.com/api/v1/resolve?ref=uze-sh/uze/conformance-debug GET https://markdownregistry.com/api/v1/blob/a5d88edd3c21c64b4bbd18b99342efbf830bea980f589d9f1d350fc43c5ef6ea
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.