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.
Install with Tessl CLI
npx tessl i github:Dokhacgiakhoa/antigravity-ide --skill agent-evaluationOverall
score
62%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that follows best practices. It clearly specifies what the skill does (testing/benchmarking LLM agents with four specific activities), includes an explicit 'Use when:' clause with natural trigger terms, and carves out a distinct niche around agent evaluation. The description uses proper third-person voice and is concise yet comprehensive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'behavioral testing, capability assessment, reliability metrics, and production monitoring'. Also includes a concrete detail about benchmark performance ('less than 50% on real-world benchmarks'). | 3 / 3 |
Completeness | Clearly answers both what (testing and benchmarking LLM agents with specific activities listed) and when (explicit 'Use when:' clause with trigger terms). The structure follows the recommended pattern. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'agent testing', 'agent evaluation', 'benchmark agents', 'agent reliability', 'test agent'. These cover common variations of how users would phrase requests about testing LLM agents. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on 'LLM agents' testing and benchmarking, distinct from general testing skills or general LLM skills. The combination of 'agent' + 'testing/evaluation/benchmark' creates a specific domain unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill content is essentially a stub—it provides a philosophical framing and links to sub-skills but offers no actionable guidance in the main file itself. The content describes the importance of agent evaluation without teaching how to do it. The sub-skill structure suggests good organization intent, but the parent skill needs substantial content to be useful.
Suggestions
Add a 'Quick Start' section with a concrete example of running a basic agent evaluation (executable code or specific commands)
Include at least one complete workflow showing the sequence of steps for evaluating an agent, with validation checkpoints
Remove the narrative persona framing ('You're a quality engineer who...') and replace with direct, actionable instructions
Add a brief summary of what each sub-skill covers so readers can navigate without clicking through all links
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The introductory narrative about being a 'quality engineer' adds unnecessary context that Claude doesn't need. The capabilities/requirements lists are reasonable but the prose could be tighter. | 2 / 3 |
Actionability | No concrete code, commands, or executable guidance provided. The content describes what agent evaluation is about but gives no specific instructions on how to actually perform any evaluation tasks. | 1 / 3 |
Workflow Clarity | No workflow or process steps are defined. The skill lists sub-skills but provides no sequence, validation checkpoints, or guidance on how to approach agent evaluation systematically. | 1 / 3 |
Progressive Disclosure | References to sub-skills are present and one-level deep, which is good. However, the main skill provides almost no overview content—it's essentially just a table of contents with no quick-start or summary of key concepts. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
91%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.