evals SKILL.md skillA
evals from renzrollon/interlock is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add renzrollon/interlock/evals@git:20261006.44860b1Pins git:20261006.44860b1 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- renzrollon/interlock
- Path
skills/evals/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261006.44860b1, committed Oct 6, 2026
- First version recorded
- Aug 26, 2026
- Size
- 8,631 bytes
- Repository stars
- 31
- License
- MIT
Author an Interlock eval case from an observed model-behaviour failure, and read a completed eval results run. Use when you have a reproduced failure — an archived proposal, a changelog entry, a run artifact, or a transcript — worth regression-testing against a real model, or when an eval run has finished and you need to know whether it is a regression, run-to-run variance, or no signal. Authoring needs cited evidence; the verdict comes from `interlock evals triage`, never from your own reading.
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
This skill covers the two jobs the eval harness does not do for you: turning an observed failure into a case, and reading a finished run. Everything with a correct answer — is this a regression? — belongs to `interlock evals triage`, not to you. Your job is evidence, grader choice, and explanation. ## 1. Authoring a case — only from an observed failure A case regression-tests a **reproduced** failure: a model read correct instructions and did the wrong thing anyway. Before you write anything, require the evidence: - an archived proposal (`openspec/changes/archive/*/proposal.md` `## Why`), - a `CHANGELOG.md` entry, - a run artifact or a transcript, - a **captured skeleton** — `interlock evals capture --run <runId> [--task <id>] --out <dir>` turns a recorded ship-run trajectory into a case draft whose provenance names the trajectory and the events it was derived from, or - a `file:line` span in the prompt or skill under test that shows the surface the model talked past. **A captured skeleton is a draft, not a finished case.** It is admissible evidence because it is a run artifact and a reader can follow its citation back …
Read the whole file at its exact version.
How to install
mdr add renzrollon/interlock/evals@sha256:9fe4f91048ee8a9dThe line at the top of this page pins the label git:20261006.44860b1, 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_aznjig5sluoodced)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Aug 26, 2026 and Oct 6, 2026, about one every 20 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261006.44860b1 latest | 2026-10-06 | 44860b1 | 8,631 B | A | view · diff |
| git:20260904.96ef819 | 2026-09-04 | 96ef819 | 8,635 B | A | view · diff |
| git:20260826.2b0c1de | 2026-08-26 | 2b0c1de | 6,375 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 (8631 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
renzrollon/interlock · 31 stars · license MIT · pushed 2026-10-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_aznjig5sluoodced GET https://markdownregistry.com/api/v1/resolve?ref=renzrollon/interlock/evals GET https://markdownregistry.com/api/v1/blob/9fe4f91048ee8a9d0c98a010993b059e961d6472b26f9a920cb89324fe71ef4f
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.
More from renzrollon/interlock
Every file in renzrollon/interlock