- Home
- Skills
- Supercent Io
- Skills Template
- Agent Evaluation
agent-evaluation_skill
- Shell
24
GitHub Stars
2
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill supercent-io/skills-template --skill agent-evaluation- SKILL.md13.0 KB
- SKILL.toon789 B
Overview
This skill guides the design and implementation of comprehensive evaluation systems for AI agents. It covers grader types (code-, model-, human-based), benchmarks for different agent classes, an 8-step roadmap for building eval suites, and how to integrate evals into production and CI/CD. Use it to create repeatable, outcome-focused, and maintainable agent evaluations.
How this skill works
The skill explains what to inspect: tasks, trials, transcripts, outcomes, and grader outputs. It prescribes grader selection and rubric design per agent type, test harness and isolation patterns, and metrics to collect (pass rates, variance, resolution rate, etc.). It also describes workflows for running suites in CI, sampling in production, A/B testing, and monitoring eval saturation and maintenance.
When to use it
- Building benchmarks for coding, conversational, research, or computer-use agents
- Designing graders and rubrics for objective scoring
- Implementing CI/CD pipelines with automated eval runs
- Setting up production monitoring and sampling for model quality
- Debugging agent behavior via transcript analysis
- Measuring improvement and detecting eval saturation
Best practices
- Start small: 20–50 representative tasks covering common, edge, and failure cases
- Prefer code-based graders for structured outputs; use model graders for nuance and humans for final validation
- Focus grading on final outcomes rather than intermediate steps
- Isolate eval environments (containers, timeouts, resource limits) to avoid flakiness
- Regularly read transcripts to identify failure modes and tool usage patterns
- Monitor saturation and retire or harden tasks when pass rates are consistently high
Example use cases
- Coding agent: run test suites, lint, build checks, and compute test-passage rate for each trial
- Conversational agent: apply a multi-dimensional rubric (empathy, resolution, efficiency) with model-based grader and aggregated scores
- Research agent: score grounding, coverage, source quality, and factual accuracy with a blend of automated checks and human review
- Computer-use agent: verify UI state, file/db state, screenshots and outcome conditions in an isolated sandbox
- CI integration: run compact eval subsets on PRs and full suites on nightly builds with artifact upload
FAQ
Use code-based graders when you can define clear, testable success criteria (fast, reproducible). Use model-based graders when outputs are open-ended or require nuance; calibrate rubrics and validate with humans. Combine graders when appropriate.
When should I sample production traffic for evals?
Sample continuously but sparsely (e.g., 5–10%) to detect regressions without excessive cost. Sanitize data, anonymize user content, and trigger alerts for scores below thresholds so you can add failing cases to the eval suite.