CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

test-quality-analysis

Detect test smells, overmocking, flaky tests, and coverage issues. Analyze test effectiveness, maintainability, and reliability. Use when reviewing tests or improving test quality.

Quality

77%

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 ./plugins/test-quality-analysis/skills/test-quality-analysis/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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 body is a well-organized, example-rich knowledge skill whose paired BAD/GOOD snippets and coverage commands are genuinely actionable. Its weaknesses are redundancy (repeated mocking guidance, textbook FIRST/AAA explanations) and the absence of a sequenced analysis workflow with validation checkpoints.

Suggestions

Add a short ordered workflow (e.g. 1. run coverage commands, 2. scan for each listed smell using the detection heuristics, 3. verify suspected flakiness by re-running, 4. report findings per dimension) so the analysis process is sequenced with checkpoints.

Merge the duplicated 'Mocking Too Much' section into the 'Overmocking' section and trim the FIRST and AAA checklists to one-line reminders, since Claude already knows these textbook concepts.

Move the extended smell catalog and coverage-tool details into a references/ file (e.g. SMELLS.md) linked from a concise overview in SKILL.md to improve both conciseness and progressive disclosure.

DimensionReasoningScore

Conciseness

Sections like the FIRST principles checklist and the AAA pattern restate concepts Claude already knows, and the "Mocking Too Much" section largely repeats the earlier "Overmocking" section's guidance. It is mostly efficient with concrete value in the code examples, matching the 3 anchor (some unnecessary explanation that could be tightened) rather than 4, where only minor trimming would be needed.

3 / 5

Actionability

Runnable commands ("bun test --coverage --coverage.thresholds.lines=80", "uv run pytest --cov --cov-report=html"), paired BAD/GOOD code examples, and concrete detection heuristics ("More than 3-4 mocks") give mostly executable guidance. The code snippets are illustrative rather than complete (e.g. `calculateTotal` is undefined), which keeps it at 4 rather than 5.

4 / 5

Workflow Clarity

The body offers dimensions, checklists, and tool commands but never sequences them into an analysis workflow (e.g. run coverage → scan for each smell → report findings), and there are no validation checkpoints confirming a smell before recommending a fix. This matches the 3 anchor (elements present but sequence/checkpoints implicit) rather than 4, which requires a clear ordered process; the destructive-operation cap is not triggered since this is a read-only analysis skill.

3 / 5

Progressive Disclosure

No bundle files exist, and the ~185-line body is well-organized with clear section headers (smells, tools, checklists, anti-patterns) and one-level "See Also" pointers to related skills. It sits at 4 rather than 5 because the body exceeds the simple-skill threshold and some material (e.g. the extended smell catalog or coverage tooling details) could live in reference files, leaving minor organization gaps.

4 / 5

Total

14

/

20

Passed

Description

83%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 strong description: concrete, domain-specific actions paired with an explicit 'Use when...' clause containing natural trigger phrases. The main improvement levers are adding a couple of missing synonyms (unit tests, test suite, mocking) and tightening the when-clause against overlap with general code-review skills.

DimensionReasoningScore

Specificity

"Detect test smells, overmocking, flaky tests, and coverage issues" and "Analyze test effectiveness, maintainability, and reliability" name several concrete actions in the domain. It falls just short of the 5 anchor because coverage is not fully comprehensive — e.g. no explicit 'fix/suggest improvements' action beyond the when-clause's 'improving test quality'.

4 / 5

Completeness

It explicitly answers both what ("Detect test smells, overmocking, flaky tests, and coverage issues. Analyze test effectiveness, maintainability, and reliability.") and when ("Use when reviewing tests or improving test quality") with concrete trigger phrases, matching the 5 anchor; a 4 would require the when-clause to be less explicit than it is.

5 / 5

Trigger Term Quality

Natural phrases users would say include "test smells", "overmocking", "flaky tests", "coverage", "reviewing tests", and "test quality". A few common variations are missing (e.g. "unit tests", "test suite", plain "mocking", "flakiness"), matching the 4 anchor of good coverage with a few natural terms missing rather than the 5 anchor's synonym-and-extension completeness.

4 / 5

Distinctiveness Conflict Risk

The test-quality niche is clear with distinct triggers like "test smells", "overmocking", and "flaky tests", but the broad when-clause "Use when reviewing tests or improving test quality" could overlap with a general code-review or testing-framework skill, matching the 4 anchor (mostly distinct, minor overlap risk) rather than the 5 anchor's minimal conflict risk.

4 / 5

Total

17

/

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

allowed_tools_field

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

Warning

Total

15

/

16

Passed

Repository

secondsky/claude-skills

Path

plugins/test-quality-analysis/skills/test-quality-analysis/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.