eval-import SKILL.md skillA
eval-import 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-import@git:20260921.b6d8d5bPins git:20260921.b6d8d5b 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-import/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260921.b6d8d5b, committed Sep 21, 2026
- First version recorded
- Sep 15, 2026
- Size
- 23,412 bytes
- Repository stars
- 133
- License
- MIT
Turn a list of questions into an eval set, whatever shape it arrived in: a JSONL a customer sent, a CSV, a spreadsheet export, a markdown doc, an email thread, or a pull from production logs. Classify each item by what came WITH the question (a query, a number, prose criteria, or nothing), write cases.jsonl and set.json per reference/case-format.md, keep the file as it arrived, and seal each question so a later edit is detectable. Never marks a value-bearing golden verified and never invents a…
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
# Import questions into an eval set Questions arrive in whatever shape their author had. This turns them into `evals/<set>/`, ready for a run, and records what each key is actually worth. **Scope boundary:** cases only. This never answers a question, scores an answer, or edits a model. It is `skill:eval-loop`'s scrape step, expanded, and it is where the set's honesty is decided. The file shapes are defined once, in `reference/ledger-schema.md` of `skill:eval-answer`. Read them there; this skill does not restate them. `reference/case-format.md` covers what is specific to an import: which fields an arriving item maps to, and the four physical formats. ## Where the set goes Two separate rules, and "package" blurs them: - **The same git repository as the model it evaluates**, so one commit pins the model and the ledger together. That is what a checkpoint is. - **Never inside the directory tree the answerer's package serves.** The answerer can read files in the served tree, and gold there is a contamination path. So the set is a SIBLING of the package under test, in its repo. A repo with `ecommerce/` under test gets `evals/ecommerce-questions/`, beside it. …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_bmrk3s243pto7wbh/bcd62b5f44eddaf6b5185224890da8940ec4481130f2b6fefdf10d96cc39107a.json
Then /plugin install eval-import@markdownregistry-bmrk3s243pto7wbh in Claude Code. It installs git:20260921.b6d8d5b, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add malloydata/publisher/eval-import@sha256:bcd62b5f44eddaf6The line at the top of this page pins the label git:20260921.b6d8d5b, 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_bmrk3s243pto7wbh)
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-import 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-import from somewhere else? Ask it: where did my eval-import 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 2 versions of this file, between Sep 15, 2026 and Sep 21, 2026, about one every 6 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260921.b6d8d5b latest | 2026-09-21 | b6d8d5b | 23,412 B | A | view · diff |
| git:20260915.7cd0a0e | 2026-09-15 | 7cd0a0e | 12,507 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-import/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 (23412 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_bmrk3s243pto7wbh GET https://markdownregistry.com/api/v1/resolve?ref=malloydata/publisher/eval-import GET https://markdownregistry.com/api/v1/blob/bcd62b5f44eddaf6b5185224890da8940ec4481130f2b6fefdf10d96cc39107a
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.