agent-evaluation
Skill177 starsChanged 7 days agoApache-2.0View on GitHub
Evaluate changes to agent instructions, skills, routing, and tools using frozen cases and reviewed evidence. Use for agent regression, prompt comparisons, recovery checks, and capability acceptance.
23 other projects use a version of this.
Adopted by
Most recently taken up by
- AtilaMedeiros/skillstheir own version, first seen Nov 16, 2026
- Ivan-propio/claude-skillstheir own version, first seen Nov 16, 2026
- JPeetz/agent-skillstheir own version, first seen Nov 15, 2026
- Azir-11/skill-hubtheir own version, first seen Nov 8, 2026
- dzianisv/opencode-pluginstheir own version, first seen Nov 1, 2026
- asmamest/Nexus-Skillstheir own version, first seen Oct 15, 2026
Used with
Projects with it also use tool-design, context-engineering and 5 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
mjunaidcaSkilltool-design
Design tools that agents can use effectively. Use when creating new tools for agents, debugging tool-related failures, or optimizing existing tool sets.
Also in 3 projects that use this
mrgoonieSkillcontext-engineering
Master context engineering for AI agent systems. Use when designing agent architectures, debugging context failures, optimizing token usage, implementing memory systems, building multi-agent coordination, evaluating agent performance, or developing LLM-powered pipelines. Covers context fundamentals, degradation patterns, optimization techniques (compaction, masking, caching), compression strategies, memory architectures, multi-agent patterns, LLM-as-Judge evaluation, tool design, and project development.
Also in 4 projects that use this
xenitV1Skillclean-code
Pragmatic coding standards - concise, direct, no over-engineering, no unnecessary comments
Also in 3 projects that use this
OpenAISkilltest-driven-development
Use when implementing any feature or bugfix, before writing implementation code
Also in 3 projects that use this
BlockSkillfrontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
Also in 3 projects that use this
GoogleSkillcode-review
Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.
Also in 3 projects that use this
Other versions23 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 23
- bojieli/ai-agent-book-projects★ 53ksame name
- bojieli/ai-agent-book★ 53ksame name
- microsoft/Building-AI-Agents-From-Zero-To-Production★ 194same name
- alebgl77/claude-inc★ 21same name
- JPeetz/agent-skills★ 17same name
- dzianisv/opencode-plugins★ 11same name
- xfstudio/skills★ 9same name
- Azir-11/skill-hub★ 7same name
- nek1987/auto-agent-harness★ 4same name
- mattstruble/skills★ 3same name
13 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository19 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- algorithm-developmentSkill
- buildSkill
- change-reviewSkill
- container-buildSkill
- engineering-solution-designSkill
- interface-migrationSkill
- issue-localizationSkill
- lintSkill
- long-horizon-developmentSkill
- model-artifact-integrationSkill
- multi-repo-devSkill
- performance-optimizationSkill
- repository-agent-setupSkill
- simulation-regressionSkill
- test-impact-analysisSkill
- unified-core-runtimeSkill
- vendorSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 19 edited versions we read keep these.
4
Distinctive
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 10
Read the evaluation procedure and select relevant cases from the case set.
- Distinctive: line 16
Run only explicitly authorized tasks.
- Distinctive: line 21
Use the evaluation command to check report structure and aggregate gate results.
- Distinctive: line 29
Keep tuning and holdout cases distinct.
“Common” is measured: kept by at least 6 in 10 of the 19 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Agent Evaluation
Procedure
- Read the evaluation procedure and select relevant cases from the case set.
- Freeze task inputs, code, context, skill/tool versions, model configuration, environment, and approvals for each comparison. Use separate worktrees or the existing isolated harness; never revert someone else's work.
- Run only explicitly authorized tasks. Preserve actual transcripts, tool results, diffs, and evidence outside durable knowledge. No automatic road/HIL operations, publication, paid runs, or agent spawning.
- Have a reviewer judge each case gate from the evidence. Record false or not-run for missing proof; an agent's own completion claim is insufficient.
- Use the evaluation command to check report structure and aggregate gate results. Compare like-for-like runs; do not present schema validation as an agent benchmark or averages as permission to ignore hard-gate failures.
Acceptance and failure handling
Report case coverage, hard-gate failures, correctness, unnecessary changes, invalid operations, recovery, cost, and human intervention when measured. Keep tuning and holdout cases distinct. Do not weaken gates after seeing a failure; version intentional criterion changes and rerun comparable baselines.
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.

