CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

unit-tests

Use when reviewing CI coverage, automated checks, or test strategy related to Write unit tests. Focus on whether the rule is continuously verified, not just documented.

Quality

72%

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/unit-tests/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 well-structured with excellent progressive disclosure: a tight overview pointing to a single real one-level-deep reference. Its weaknesses are a known-concept intro paragraph redundant with the Explain section, and generic Check/Fix guidance that defers all executable detail to the reference.

Suggestions

Delete the opening benefits paragraph and fold the redundant "## Explain" content into it, or replace both with one line of non-obvious guidance — Claude already knows why unit tests matter.

Inline one short executable anchor in the body (e.g., a coverage-check command or a minimal test skeleton) so the Check/Fix steps are immediately actionable before jumping to references/rule.md.

DimensionReasoningScore

Conciseness

The opening paragraph ("Unit tests catch bugs before they reach production, serve as documentation for expected behavior...") explains benefits Claude already knows, and the "## Explain" section ("Explain how unit tests catch bugs early and serve as documentation for expected behavior") duplicates it. The rest of the body is lean, so this is some unnecessary explanation rather than several padded sections, fitting anchor 3 rather than 2 or 4.

3 / 5

Actionability

The Quick Reference gives concrete heuristics ("Test business logic, utilities, and edge cases", "Aim for 80%+ coverage on critical paths", "Mock external dependencies, not internal modules"), but the Check/Fix directives ("Write unit tests for untested functions and components") are high-level and all code and examples are deferred to the reference file. Some concrete guidance, incomplete in the body itself — anchor 3, below 4 (no executable code or commands present) and above 2 (more than vague hints).

3 / 5

Workflow Clarity

The Check → Fix → Code Review sections form a clear, unambiguous sequence for a simple single-purpose skill, with "Run tests in CI to catch regressions early" hinting at the verification endpoint. Verification checkpoints (run the coverage tool, confirm new tests pass) remain implicit rather than explicit steps, which keeps it below anchor 5 while the simple-skill exception keeps it above anchor 3's validation-gap level.

4 / 5

Progressive Disclosure

The body is a short, well-sectioned overview that defers all implementation detail via a single clearly signaled one-level-deep pointer: "For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`" — a real file (484 lines) with no further nested references. This matches the anchor for a clear overview with well-signaled, appropriately split references and easy navigation.

5 / 5

Total

15

/

20

Passed

Description

70%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 has an explicit, well-formed trigger clause with natural keywords and a distinctive verification-focused framing. Its main weaknesses are a modest set of concrete capability actions and an awkward, blended what/when construction ("related to Write unit tests").

Suggestions

Lead with a concrete capability statement (e.g., "Reviews test suites, coverage reports, and CI gates for unit-test rules") before the 'Use when' clause, so the 'what' stands on its own.

Add natural trigger variations such as "test coverage", "test suite", or "regression tests" to broaden keyword coverage toward the top anchor.

DimensionReasoningScore

Specificity

"reviewing CI coverage, automated checks, or test strategy" and "Focus on whether the rule is continuously verified" name the domain and 1-2 concrete actions, but the description does not list several distinct specific actions. It sits above anchor 2 (domain named with only generic actions) and below anchor 4 (multiple specific concrete actions listed).

3 / 5

Completeness

An explicit "Use when reviewing CI coverage, automated checks, or test strategy..." clause answers when, and "Focus on whether the rule is continuously verified, not just documented" answers what. Both are present (satisfying the 'Use when...' requirement), but the what is a focus clause embedded in the when-sentence rather than a clear leading capability statement, and "related to Write unit tests" is awkward phrasing, keeping it below anchor 5.

4 / 5

Trigger Term Quality

"CI coverage", "automated checks", "test strategy", and "unit tests" are natural phrases users would say when needing this skill, giving good keyword coverage. Missing common variations like "test coverage", "test suite", or "regression", so it falls short of anchor 5's comprehensive synonym coverage but exceeds anchor 3's bare single-keyword level.

4 / 5

Distinctiveness Conflict Risk

The niche framing "whether the rule is continuously verified, not just documented" scoped to unit tests makes it mostly distinct from other skills. Terms like "test strategy" and "automated checks" carry minor overlap risk with general testing/CI skills, so it does not reach anchor 5's clear niche with minimal conflict risk.

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

thedaviddias/Front-End-Checklist

Path

skills/unit-tests/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.