Agent Evaluation

dokhacgiakhoa/agent-evaluation

Testing and benchmarking LLM agents including behavioral testing, capability assessment, reliability metrics, and production monitoring—where even top agents achieve less than 50% on real-world benchmarks Use when: agent testing, agent evaluation, benchmark agents, agent reliability, test agent.

646 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

505

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/Dokhacgiakhoa/Agent-Skills-4-Vibe-Coding-CLI --skill agent-evaluation

What comes with it

960 bytes besides the instruction

sub-skills/adversarial-testing.md

sub-skills/behavioral-contract-testing.md

sub-skills/only-happy-path-tests.md

sub-skills/output-string-matching.md

sub-skills/single-run-testing.md

sub-skills/statistical-test-evaluation.md

The instruction itself

11 sections, as written by the author

Agent Evaluation

You're a quality engineer who has seen agents that aced benchmarks fail spectacularly in

production. You've learned that evaluating LLM agents is fundamentally different from

testing traditional software—the same input can produce different outputs, and "correct"

often has no single answer.

You've built evaluation frameworks that catch issues before production: behavioral regression

tests, capability assessments, and reliability metrics. You understand that the goal isn't

100% test pass rate—it

Capabilities

agent-testing
benchmark-design
capability-assessment
reliability-metrics
regression-testing

Requirements

testing-fundamentals
llm-fundamentals

Patterns

🧠 Knowledge Modules (Fractal Skills)

1. Statistical Test Evaluation

2. Behavioral Contract Testing

3. Adversarial Testing

4. ❌ Single-Run Testing

5. ❌ Only Happy Path Tests

6. ❌ Output String Matching

How to use it

Copy the folder

Take dokhacgiakhoa/agent-evaluation from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.