CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

65

Quality

78%

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

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.

A well-structured, actionable reference of test-quality guidance with concrete code examples and checklists. Its main gaps are repeated anti-pattern sections and the absence of a sequenced review workflow with validation checkpoints.

Suggestions

Merge the overlapping 'Test Smells' and 'Common Anti-Patterns' sections to remove duplication between Overmocking/Mocking Too Much and Fragile Tests/Testing Implementation Details.

Add a short sequenced review workflow with a validation checkpoint, e.g. 1. run coverage, 2. scan for smells, 3. verify fixes re-pass deterministically.

Make code examples self-contained or note that helper functions are illustrative, so snippets are copy-paste ready.

DimensionReasoningScore

Conciseness

Mostly lean with no basic-concept padding, but 'Overmocking' / 'Mocking Too Much' and 'Fragile Tests' / 'Testing Implementation Details' repeat the same guidance, so not every token earns its place.

4 / 5

Actionability

Concrete, executable TypeScript and bash examples with specific detection heuristics ('More than 3-4 mocks', 'Mock only I/O boundaries'), but several snippets reference undefined functions (calculateTotal, registerUser, calculateDistance) so they are not fully copy-paste self-contained.

4 / 5

Workflow Clarity

Provides checklists and tool commands but no sequenced analysis workflow with validation checkpoints — there is no 'run coverage → identify smells → report' process, only loosely ordered lists.

3 / 5

Progressive Disclosure

Well-organized into clearly headed sections with a See Also pointer to sibling skills; no bundle files exist so all content is inline, which is reasonable at this length though some detail could be split into reference files.

4 / 5

Total

15

/

20

Passed

Description

88%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, specific description that clearly states capabilities and an explicit use-when trigger. It is comprehensive on the test-quality domain with only minor overlap risk against sibling testing skills and a few missing natural synonyms.

Suggestions

Add common synonyms a user might actually say, e.g. 'Use when reviewing unit tests, tightening a flaky test suite, or raising test coverage.'

Tighten the trigger to reduce overlap with sibling testing skills, e.g. 'Use when diagnosing test smells or assessing test quality — not for writing new tests.'

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions across the test-quality domain — 'Detect test smells, overmocking, flaky tests, and coverage issues' plus 'Analyze test effectiveness, maintainability, and reliability' — giving comprehensive coverage rather than a few actions with gaps.

5 / 5

Completeness

Explicitly answers both what (detect/analyze specific test-quality concerns) and when ('Use when reviewing tests or improving test quality') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural keyword coverage ('reviewing tests', 'improving test quality', 'flaky tests', 'coverage') but misses common synonyms a user might say ('unit tests', 'test suite', 'test review'); no file extensions apply here.

4 / 5

Distinctiveness Conflict Risk

Clear test-quality niche with distinct triggers, but the fairly broad 'reviewing tests or improving test quality' phrasing carries minor overlap risk with closely related sibling testing skills (vitest-testing, mutation-testing).

4 / 5

Total

18

/

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

allowed_tools_field

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

Warning

Total

15

/

16

Passed

Repository
secondsky/claude-skills
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.