eval-improve SKILL.md skillA
eval-improve from malloydata/publisher is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add malloydata/publisher/eval-improve@git:20261111.2af71bcPins git:20261111.2af71bc in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- malloydata/publisher
- Path
skills/eval-improve/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261111.2af71bc, committed Nov 11, 2026
- First version recorded
- Sep 3, 2026
- Size
- 13,922 bytes
- Repository stars
- 133
- License
- MIT
Make the smallest safe edit that closes a diagnosed gap the model repo owns: a Malloy model edit, or a package skill under skills/. Every factual claim carries a probe receipt. Use after eval-diagnose, or when asked to fix a model so an agent can discover the right answer. Never accepts its own edit; the acceptance check belongs to eval-loop. Does not decide whether an answer was wrong (eval-answer) or why (eval-diagnose).
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
# Improve the Model Takes an issue with `owner: model` or `owner: package-skill` and produces **one smallest edit** that closes the gap. Every factual claim is backed by a query you ran. The two owners license different edits and are never interchangeable: - **`model`** changes what the data means or how it is described: a `.malloy` file. - **`package-skill`** changes what the agent is told about using this package: a file under the package's `skills/`. Use it for a rule that spans entities or is not a property of any one of them. A fact about a single field belongs in that field's `#(doc)`, which reaches every agent whether or not it loaded a guide. Both live in the model repo, so one git commit checkpoints and rolls back either. **Two hard boundaries:** 1. **No diagnosis evidence, no edit.** If the issue cannot name a concrete gap with a trace or probe, record that and stop. Edits from an empty diagnosis have been the inert and wrong ones. 2. **This skill never accepts its own edit.** You propose and verify. The acceptance check in `skill:eval-loop` admits or reverts. An improver writing the query it …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_xos7dgi6uvyjda5h/836a093df73267517c6aaf0affe63acb85b012600972f345caacd34859f14da7.json
Then /plugin install eval-improve@markdownregistry-xos7dgi6uvyjda5h in Claude Code. It installs git:20261111.2af71bc, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add malloydata/publisher/eval-improve@sha256:836a093df7326751The line at the top of this page pins the label git:20261111.2af71bc, 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_xos7dgi6uvyjda5h)
1 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in malloydata/publisher/eval-improve since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of eval-improve from somewhere else? Ask it: where did my eval-improve come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 5 versions of this file, between Sep 3, 2026 and Nov 11, 2026, about one every 17 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261111.2af71bc latest | 2026-11-11 | 2af71bc | 13,922 B | A | view · diff |
| git:20261015.83c83b7 | 2026-10-15 | 83c83b7 | 13,769 B | A | view · diff |
| git:20261012.9b94813 | 2026-10-12 | 9b94813 | 13,468 B | A | view · diff |
| git:20260915.7cd0a0e | 2026-09-15 | 7cd0a0e | 11,202 B | A | view · diff |
| git:20260903.3bc4086 | 2026-09-03 | 3bc4086 | 8,956 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/eval-improve/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
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 (13922 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
malloydata/publisher · 133 stars · license MIT · pushed 2026-11-17 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_xos7dgi6uvyjda5h GET https://markdownregistry.com/api/v1/resolve?ref=malloydata/publisher/eval-improve GET https://markdownregistry.com/api/v1/blob/836a093df73267517c6aaf0affe63acb85b012600972f345caacd34859f14da7
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.