evaluate-agent
Skill4 starsChanged 53 days agoMITView on GitHub
Evaluate an agent against explicit capability, safety and regression criteria without inventing missing evidence. Benchmark cases, outputs or traces, expected labels and optional release thresholds. Run deterministic checks first, measure relevant rates, separate observations from interpretation and report passed, failed and unresolved gates. Required fixtures are missing, required traces are unavailable, unauthorized access would be needed, or the requested conclusion exceeds the evidence. A structured evaluation summary with metrics, failures, uncertainty and evidence references.
In this repository2 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
Run deterministic checks first, measure relevant rates, separate observations from interpretation and report passed, failed and unresolved …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Objective
Evaluate an agent against explicit capability, safety and regression criteria without inventing missing evidence.
Inputs
Benchmark cases, outputs or traces, expected labels and optional release thresholds.
Procedure
Run deterministic checks first, measure relevant rates, separate observations from interpretation and report passed, failed and unresolved gates.
Failure conditions
Required fixtures are missing, required traces are unavailable, unauthorized access would be needed, or the requested conclusion exceeds the evidence.
Evidence produced
A structured evaluation summary with metrics, failures, uncertainty and evidence references.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

