agentic-eval SKILL.md skillA
agentic-eval from jpeetz/agent-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add jpeetz/agent-skills/agentic-eval@v1.0.0Pins v1.0.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- jpeetz/agent-skills
- Path
skills/ai-agent-engineering/agentic-eval/SKILL.md- Versions recorded
- 1
- Latest version
- v1.0.0, committed Nov 14, 2026
- Size
- 31,802 bytes
- Repository stars
- 17
- License
- none declared
Use this skill when setting up or improving evaluation for AI agents and LLM outputs. Activates on "agent eval", "LLM evaluation", "eval harness", "agent benchmark", "rubric judge", "evaluator-optimizer", "self-critique", "LLM as judge", "pairwise rank", "eval pipeline", "calibration test", "agentic eval", or "eval-driven development". Covers rubric design, evaluator-optimizer architecture, self-critique loops, pairwise ranking, calibration, eval harness setup, and continuous eval pipelines.
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
# Agentic Eval ## Overview An agent that "seems good" in a demo is an untested agent. Evaluation is how you replace that impression with a number you can act on: a fixed set of cases, a scoring procedure, and a baseline you compare against before every change. Without it you cannot tell a prompt rewrite that helped from one that merely felt better, and you ship regressions you never saw. Three things make agent evals different from ordinary unit tests: - **The output space is open.** There is rarely one correct string, so correctness has to be defined by criteria, not equality. - **Trajectory matters.** An agent that reaches the right answer after seven wrong tool calls is a worse agent than one that reaches it in two. Score the path, not just the final text. - **The judge is often a model.** That judge has biases — verbosity, position, self-preference — and it drifts. A judge you have not calibrated is a random number generator with good vocabulary. …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_z5ivxjkq37ckdwix/bfe8420527a1c3859fc60835a1689cd4ec50aeb8e5bfa13762f0848fadc7d027.json
Then /plugin install agentic-eval@markdownregistry-z5ivxjkq37ckdwix in Claude Code. It installs v1.0.0, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add jpeetz/agent-skills/agentic-eval@sha256:bfe8420527a1c385The line at the top of this page pins the label v1.0.0, 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_z5ivxjkq37ckdwix)
3 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 jpeetz/agent-skills/agentic-eval 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 agentic-eval from somewhere else? Ask it: where did my agentic-eval 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 1 version of this file, committed on Nov 14, 2026.
Watch this file (sign in, one email per new version)
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/agentic-eval/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 (31802 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
jpeetz/agent-skills · 17 stars · license none declared · pushed 2026-11-16 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_z5ivxjkq37ckdwix GET https://markdownregistry.com/api/v1/resolve?ref=jpeetz/agent-skills/agentic-eval GET https://markdownregistry.com/api/v1/blob/bfe8420527a1c3859fc60835a1689cd4ec50aeb8e5bfa13762f0848fadc7d027
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 jpeetz/agent-skills
Every file in jpeetz/agent-skills