plugins/toolkit/skills/anthropic-evaluations/SKILL.md
This skill should be used when the user asks to "create evals", "evaluate an agent", "build evaluation suite", or mentions agent testing, graders, or benchmarks. Also suggest when building coding agents, conversational agents, or research agents that need quality assurance.
npx skillsauth add dwmkerr/claude-toolkit anthropic-evaluationsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Build rigorous evaluations for AI agents using Anthropic's proven patterns.
You MUST read the reference files for detailed guidance:
YAML Templates:
Annotated Examples:
| Term | Definition | |------|------------| | Task | Single test with defined inputs and success criteria | | Trial | One attempt at a task (run multiple for consistency) | | Grader | Logic that scores agent performance; tasks can have multiple | | Transcript | Complete record of a trial (outputs, tool calls, reasoning) | | Outcome | Final state in environment (not just what agent said) | | Evaluation harness | Infrastructure that runs evals end-to-end | | Agent harness | System enabling model to act as agent (scaffold) | | Evaluation suite | Collection of tasks measuring specific capabilities |
| Type | Methods | Best For | |------|---------|----------| | Code-based | String match, unit tests, static analysis, state checks | Fast, cheap, objective verification | | Model-based | Rubric scoring, assertions, pairwise comparison | Nuanced, open-ended tasks | | Human | SME review, A/B testing, spot-check sampling | Gold standard calibration |
See Grader Types for detailed comparison.
| Type | Question | Target Pass Rate | |------|----------|------------------| | Capability | "What can this agent do well?" | Start low, hill-climb | | Regression | "Does it still handle what it used to?" | Near 100% |
Capability evals with high pass rates "graduate" to regression suites.
| Metric | Measures | Use When | |--------|----------|----------| | pass@k | At least 1 success in k attempts | One success matters (coding) | | pass^k | All k attempts succeed | Consistency essential (customer-facing) |
Example: 75% per-trial success rate
tracked_metrics:
- type: transcript
metrics: [n_turns, n_toolcalls, n_total_tokens]
- type: latency
metrics: [time_to_first_token, output_tokens_per_sec, time_to_last_token]
Based on Demystifying evals for AI agents by Anthropic (January 2026).
tools
This skill should be used when the user asks to "create a skill", "write a skill", "build a skill", or wants to add new capabilities to Claude Code. Use when developing SKILL.md files, organizing skill content, or improving existing skills. Do NOT use for plugin development, hook creation, agent creation, or slash command creation — those have dedicated skills.
development
This skill should be used when the user asks to "create a bash script", "write a shell script", or mentions shell scripting conventions.
development
Deep research into technical solutions by searching the web, examining GitHub repos, and gathering evidence. Use when the user explicitly says "use the research skill", "use a research agent", or asks for deep/thorough research into implementation options or technologies.
tools
This skill should be used when the user asks to "set up release please", "configure automated releases", "manage version numbers", "add changelog automation", or mentions release-please, semantic versioning, or monorepo versioning.