Skill Evaluation#
Moving from “it feels better” to “I have proof” when measuring AI agent skill quality.
The Problem#
LLM agents are non-deterministic. Manual testing captures one sample from a distribution. “Vibes-based” evaluation misses regressions, false positives, and edge cases. As Karpathy noted: “The eval is often harder than the task itself.”
Three-Tier Framework#
| Tier | Method | Cost | Frequency | Catches |
|---|---|---|---|---|
| 1 | Deterministic graders | ~$0 | Every commit | Command execution, file existence, sequence, format |
| 2 | LLM-as-judge | $0.01–0.20/eval | PRs, nightly | Code quality, conventions, readability (rubric-based) |
| 3 | Human review | $0.50–5.00/eval | Sparingly | Calibration, edge cases, high-stakes decisions |
“The best eval is one that actually gets run.” — Anthropic
Four Categories of Success Criteria#
- Outcome: Did the task complete? Is the output correct?
- Process: Did the agent invoke the right skill? Follow intended steps?
- Style: Does output follow conventions?
- Efficiency: No thrashing? Reasonable token usage?
Every criterion must be binary and programmatically checkable.
Test Design#
- 20–50 prompts per skill minimum
- Include negative controls (prompts that should NOT trigger the skill)
- Use pass@k metrics (probability of success in k attempts) — run 5–10x minimum
- Feed production failures back into eval sets continuously
LLM-as-Judge Pitfalls#
- Position bias (prefers first/last options)
- Verbosity bias (longer = higher scores)
- Self-preference (models prefer own family’s output)
- Inconsistency (same input, different scores across runs)
- GPT-4 class: 70–85% agreement with human evaluators
What’s Missing in the Ecosystem#
The ten-pillars-agentic-skill-design paper explicitly acknowledged “no original controlled study” as a limitation. The key-insights-agentic-landscape analysis identified evaluation as a top gap. This framework provides the methodology to fill that gap, but no tool in the wiki has fully implemented it yet.
Concrete Instances: Graph-Based Validation#
The three-tier framework applies to multiple domains of graph-based quality assurance:
Knowledge Graph Validation#
kg-validation-hybrid-workflows applies three-tier framework to fact-checking:
- Tier 1: Automated transformer & ontology validators (deterministic graders)
- Tier 2: LLM validators as second opinion (LLM-as-judge)
- Tier 3: Human experts on disagreement (selective human review)
Result: F1 score improved from 77% to 82% with <13% human effort.
Code Dependency Analysis#
ai-dependency-graph-analysis applies same framework to change impact assessment:
- Tier 1: Static AST analysis for explicit dependencies (deterministic)
- Tier 2: AI/ML scoring for breaking changes, semantic significance (85% accuracy)
- Tier 3: Human approval on high-risk changes, canary → auto-rollback on anomalies
Result: 40% reduction in production outages via tiered escalation + real-time monitoring.
Key insight: Both domains demonstrate that tier-based escalation (human-only-on-disagreement) optimizes for quality without proportional labor increase.
See Also#
- ten-pillars-agentic-skill-design
- agent-skills-standard
- prompt-engineering-patterns
- key-insights-agentic-landscape
- agent-benchmarks
- promptfoo
- kg-validation-hybrid-workflows (three-tier framework applied to knowledge graph validation)
- ai-dependency-graph-analysis (three-tier framework applied to code impact analysis)
- human-in-the-loop (escalation strategy unifies both instances)
- dependency-graphs (related tool/concept)