CtrlK
BlogDocsLog inGet started
Tessl Logo

eval-harness

Framework formal de evaluación para sesiones de Claude Code que implementa principios de desarrollo orientado a evals (EDD)

54

Quality

61%

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 ./docs/es/skills/eval-harness/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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.

The content is well-structured and actionable with concrete eval templates, grader examples, and integration commands. Its main weakness is the evaluation workflow, which lacks explicit validation/feedback-loop checkpoints despite covering batch and regression operations.

Suggestions

Add explicit validation checkpoints to the 'Evaluar' step, e.g., 'if an eval fails, record the failure, fix the code, and re-run until PASS' to establish a feedback loop.

Replace placeholder directives like '[Ejecutar cada eval de capacidad, registrar PASS/FAIL]' with a concrete runnable command or a precise sub-procedure.

Consider moving the longer template catalogs (eval types and grader types) into a reference file under references/ and linking to it from SKILL.md to improve progressive disclosure.

DimensionReasoningScore

Conciseness

The body is mostly efficient, using templates and code blocks rather than prose, with only minor restatements of obvious ideas ('Los evals lentos no se ejecutan'); it avoids explaining concepts Claude already knows.

4 / 5

Actionability

Provides concrete, copy-pasteable templates and commands (grep/npm checks, [CAPABILITY EVAL] blocks, /eval define|check|report with file paths), with only minor gaps from placeholder names like 'feature-name'.

4 / 5

Workflow Clarity

The 'Flujo de Trabajo' section lists a clear 4-step sequence (Definir → Implementar → Evaluar → Reportar), but the Evaluar step uses a placeholder ('[Ejecutar cada eval...]') and lacks explicit validation checkpoints or fix-and-retry feedback loops, which the rubric caps at 3 for batch/regression operations.

3 / 5

Progressive Disclosure

Single, well-organized SKILL.md with clear section headers and no nested references; slightly above a 3 because structure is good, though a few dense template sections could justify a separate reference file.

4 / 5

Total

15

/

20

Passed

Description

53%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.

The description states a clear domain and niche but stops short of listing concrete actions or an explicit 'Use when...' trigger. It is mostly distinct from other skills yet incomplete on the 'when' dimension.

Suggestions

Add concrete action verbs (e.g., 'Define, run, and track evals') to raise specificity beyond the abstract 'framework' phrasing.

Append an explicit 'Use when...' clause with natural triggers such as 'when setting up evals, measuring agent reliability, or comparing model versions'.

Include common trigger synonyms users might say (e.g., 'tests', 'regression suites', 'pass@k') to broaden natural keyword coverage.

DimensionReasoningScore

Specificity

Names the domain ('framework formal de evaluación para sesiones de Claude Code') and one concrete concept ('desarrollo orientado a evals (EDD)'), but lists no concrete actions like define/run/measure; slightly above the minimal-actions anchor of 2.

3 / 5

Completeness

Provides a clear 'what' (an eval framework implementing EDD) but no explicit 'when'/'Use when...' trigger clause; per the rubric a missing trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Includes relevant terms ('evals', 'EDD', 'Claude Code', 'evaluación') but omits common natural variations users might say such as 'tests', 'reliability', or 'pass@k', matching the 'some relevant keywords but missing variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The 'desarrollo orientado a evals (EDD)' niche is fairly specific and unlikely to fire for unrelated skills, with only minor overlap risk against general testing skills.

4 / 5

Total

13

/

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.

Validation15 / 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
affaan-m/ECC
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.