CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

test-evidence-review

Quality review of test files and evidence — goes beyond existence, evaluates assertion coverage. ADEQUATE/INCOMPLETE/MISSING/NOT ASSESSED per story.

Quality

68%

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 ./.claude/skills/test-evidence-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%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 strongly actionable, well-sequenced review workflow with genuine validation checkpoints and an explicit verdict taxonomy. The main weaknesses are repeated meta-rationale blockquotes that pad the token budget and an all-in-one monolithic body that could offload the report template and engine path mappings to reference files.

Suggestions

Compress the three rationale blockquotes (Section 2 empty-scope guard, Section 6 NOT ASSESSED notes) to one or two lines each — the verdict table and ranking rules already carry the operational content.

Move the full report template and the per-engine test-root mappings into a reference file (e.g. references/report-template.md) and link to it, keeping SKILL.md as the overview.

Tighten heuristic checks (date coverage, formula traceability) into concrete commands or explicit comparison steps to close the remaining actionability gap.

DimensionReasoningScore

Conciseness

The operational core is dense and assumes Claude's competence (no basic-concept teaching), but three multi-paragraph rationale blockquotes (~50 of 360 lines) repeatedly restate the same evidence-gates-closure reasoning and could be compressed to a line each.

3 / 5

Actionability

Guidance is highly concrete — exact grep patterns with -A flags, per-engine test roots, numeric assertion thresholds, a runnable review-receipts.sh command, and a copy-paste report template — with only minor heuristic gaps (e.g. "compare against sprint start date" leaves method to judgment).

4 / 5

Workflow Clarity

A clear 7-step sequence with explicit validation checkpoints: a zero-story guard with routing to sibling skills, stated-path-first with fallback search, stale-evidence receipt checks via script, explicit verdict-ranking aggregation rules, and a per-story checklist template.

5 / 5

Progressive Disclosure

No bundle files exist and all external references (coding-standards.md, test-standards.md, directory-structure.md) are clearly signaled inline, but the ~360-line body inlines content that would fit reference files (the full report template, verdict policy, engine path mappings) rather than splitting it.

3 / 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 clearly states what the skill does and is appropriately distinct from related existence-check skills, but it lacks any explicit "when to use" trigger guidance and misses several natural trigger phrases. Adding a Use-when clause with natural QA/test-quality phrasing would lift the two capped dimensions.

Suggestions

Append an explicit trigger clause, e.g. "Use when reviewing test quality before story sign-off, when tests exist and pass but coverage is in question, or as part of QA hand-off or milestone review."

Add natural trigger terms users would actually say — "test quality", "test coverage", "QA review", "evidence review", "sign-off" — alongside the existing technical terms.

Briefly enumerate the concrete checks performed (assertion coverage, edge cases, naming, sign-off completeness) to broaden the action coverage beyond the single "evaluates assertion coverage" action.

DimensionReasoningScore

Specificity

"Quality review of test files and evidence" names the domain and "evaluates assertion coverage" is one concrete action, but "goes beyond existence" is comparative framing rather than an action, so coverage is not comprehensive enough for anchor 4.

3 / 5

Completeness

The "what" is clear (quality review evaluating assertion coverage), but there is no "Use when..." clause or equivalent trigger guidance; per the rubric guideline a missing when-clause caps this dimension at 3.

3 / 5

Trigger Term Quality

Terms like "test files", "evidence", and "assertion coverage" are relevant, but common natural phrasings users would say ("test quality", "QA review", "sign-off") are missing, matching the 'some relevant keywords but missing variations' anchor.

3 / 5

Distinctiveness Conflict Risk

"Goes beyond existence" plus the distinctive verdict vocabulary (ADEQUATE/INCOMPLETE/MISSING/NOT ASSESSED) carves a niche separate from an existence-checking sibling skill, with only minor overlap risk against generic test-review skills.

4 / 5

Total

13

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository

Donchitos/Claude-Code-Game-Studios

Path

.claude/skills/test-evidence-review/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.