CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

agent-eval

Head-to-head comparison of coding agents (Claude Code, Aider, Codex, etc.) on custom tasks with pass rate, cost, time, and consistency metrics

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/agent-eval/SKILL.md

The canonical home for this skill is agent-eval in affaan-m/ECC

SKILL.md
Quality
Evals
Security

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, action-oriented body whose CLI examples, task YAML, and expected report output make the core workflow immediately executable. The main gaps are the placeholder Installation section (no install command) and the absence of error-recovery guidance when runs fail or judge results conflict.

Suggestions

Replace the Installation note with the actual install command (e.g. pip/git clone + PATH setup) so the run/report commands are executable end-to-end.

Add a short error-handling step after running agents — what to do when a run fails, times out, or judge results conflict across trials.

Consider moving the judge-type YAML schemas to a reference file and linking it, keeping SKILL.md as a tighter overview.

DimensionReasoningScore

Conciseness

The body is lean and dominated by executable YAML and CLI examples; only minor padding remains (the 'runs on vibes — this tool systematizes it' editorializing and a 'When to Activate' section that duplicates the description).

4 / 5

Actionability

Concrete, runnable commands ('agent-eval run --task tasks/add-retry-logic.yaml --agent claude-code --agent aider --runs 3', 'agent-eval report --format table') plus complete task and judge YAML examples cover the common cases, but the Installation section contains only a note with no actual install command, leaving the tool not runnable from the skill alone.

4 / 5

Workflow Clarity

A clear three-step sequence (Define Tasks → Run Agents → Compare Results) with per-run sub-steps, and judge criteria act as validation checkpoints on every run; it falls short of 5 only because there is no error-recovery guidance for failed runs or conflicting judge results.

4 / 5

Progressive Disclosure

With no bundle files present, the ~140-line body is well organized into appropriately sized sections (Core Concepts, Workflow, Judge Types, Best Practices) with no buried references; it is above the under-50-line simple-skill case, and some material (judge-type YAML schemas) could still be split into reference files.

4 / 5

Total

16

/

20

Passed

Description

66%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A specific, distinctive description that clearly states what the skill does and enumerates its metrics, but it entirely lacks 'when to use it' guidance, which both caps completeness and weakens its trigger-term profile. Adding an explicit 'Use when...' clause with natural synonyms like 'benchmark' or 'evaluate coding agents' would lift two dimensions.

Suggestions

Add an explicit trigger clause, e.g. 'Use when comparing, benchmarking, or evaluating coding agents for a team or before adopting a new tool/model.'

Include natural synonyms users would say — 'benchmark', 'evaluate agents', 'agent comparison', 'A/B test agents' — to improve trigger-term coverage.

Mention the concrete output artifact (e.g. a comparison table/report) to sharpen the 'what' beyond the metric list.

DimensionReasoningScore

Specificity

The description names concrete elements — 'Head-to-head comparison of coding agents', '(Claude Code, Aider, Codex, etc.)', and four specific metrics 'pass rate, cost, time, and consistency' — but rests on a single action verb ('comparison'), so it stops short of the comprehensive multi-action coverage of a 5.

4 / 5

Completeness

The 'what' is clear and specific (head-to-head agent comparison with named metrics), but there is no 'Use when...' clause or equivalent trigger guidance anywhere, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

'coding agents', 'Claude Code, Aider, Codex' are natural phrases users would say when needing this skill, but common synonyms like 'benchmark', 'evaluate agents', or 'agent comparison' are missing, keeping it below comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

The niche — empirical benchmarking of coding agents with pass rate/cost/time/consistency metrics — is distinct from most skills, with only minor overlap risk against generic benchmarking or testing skills, and lacks the explicit trigger phrases that would justify a 5.

4 / 5

Total

15

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

valeriibeck-star/claude-skills

Path

skills/agent-eval/SKILL.md

Reviewed

Table of Contents

Is this your skill?

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.