CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

mock-best-practices

Use when reviewing CI coverage, automated checks, or test strategy related to Follow mocking best practices. Focus on whether the rule is continuously verified, not just documented.

Quality

76%

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/mock-best-practices/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%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 lean, well-structured skill body that appropriately keeps its bulk in a single verified reference file. Its weaknesses are the absence of any validation/verification checkpoint in the Check-to-Fix flow and slightly abstract directives ('right level of abstraction') where concrete criteria or an inline snippet would help.

Suggestions

Add an explicit verification step to the workflow, e.g., after Fix: 'Re-run the affected test suite and confirm it fails when the mock is removed' — a feedback loop that catches over-mocked or broken tests.

Replace abstract directives like 'mocking at the right level of abstraction' with concrete criteria (e.g., 'mock at the network/module boundary, not inside business logic') or one inline example before deferring to the reference.

Trim the opening sentence that explains why over-mocking is bad — Claude already knows this — and keep only the rule framing needed for the review task.

DimensionReasoningScore

Conciseness

The body is tight: terse section directives, a lean Quick Reference of actionable bullets, and no padded library comparisons or explanations of what jest/MSW are. The single framing sentence ('Proper mocking isolates units under test... false confidence') explains a concept Claude already knows and could be trimmed, which is exactly the 'minor instances of over-explanation' of score 4 rather than the every-token-earns-its-place of score 5.

4 / 5

Actionability

Concrete, executable specifics are present: 'jest.restoreAllMocks() in afterEach', 'Use MSW', and named mock targets (APIs, databases, file system), plus specific check directives ('over-mocking, missing mock cleanup, proper mock implementation'). It falls short of score 5 because directives like 'mocking at the right level of abstraction' and 'proper mock implementation' are abstract, and no inline example is given — code examples live entirely in the reference file.

4 / 5

Workflow Clarity

The sections (Quick Reference, Check, Fix, Explain, Code Review) read as parallel modes with only an implicit Check-then-Fix sequence, and there are no validation or verification checkpoints anywhere (e.g., re-run tests after cleanup changes, confirm the CI check actually fails on a regression). This is not a destructive/batch operation so the hard cap does not apply, but the missing checkpoints match anchor 3; it is not score 4 because no explicit sequence or feedback loop is present.

3 / 5

Progressive Disclosure

The ~35-line body is a clean overview: each section is short, and full implementation details are clearly signaled one level deep via 'For full implementation details, code examples, and framework-specific guidance, see references/rule.md', which exists as a real 165-line file containing exactly those code examples. This matches the anchor of a clear overview with a well-signaled, one-level-deep reference and easy navigation.

5 / 5

Total

16

/

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.

A functional description with an explicit 'Use when' trigger clause and a clear focus statement on continuous verification. Its main weaknesses are a weakly stated 'what' (capabilities are implied via 'Focus on...' rather than listed) and an awkward template artifact ('related to Follow mocking best practices') that reads unnaturally.

Suggestions

State the 'what' explicitly with concrete actions, e.g., 'Reviews test files and CI workflows for mocking anti-patterns, missing mock cleanup, and unenforced rules. Use when reviewing CI coverage, automated checks, or test strategy related to mocking best practices.'

Remove the template artifact where the rule title is spliced into the sentence ('related to Follow mocking best practices') so the trigger reads naturally.

Add common trigger synonyms such as 'unit tests', 'test doubles', or 'over-mocking' to broaden natural keyword coverage.

DimensionReasoningScore

Specificity

The description names the domain ("reviewing CI coverage, automated checks, or test strategy") and one concrete action ("Focus on whether the rule is continuously verified"), but 'reviewing' is really a single generic verb applied to several objects rather than a list of distinct specific actions. It is not score 4 because it never enumerates what the skill concretely does (e.g., flag over-mocking, check mock cleanup, review enforcement points).

3 / 5

Completeness

The 'when' is explicit ("Use when reviewing CI coverage, automated checks, or test strategy..."), and a 'what' is present but indirect ("Focus on whether the rule is continuously verified, not just documented"). The 'Use when' clause is present so the score-3 cap does not apply, but the 'what' never states the skill's capabilities concretely, so it falls short of the fully explicit what+when of score 5.

4 / 5

Trigger Term Quality

Includes natural terms users would say: "reviewing", "CI coverage", "automated checks", "test strategy", "mocking best practices", "continuously verified". Missing a few common variations such as "unit tests", "test doubles", "jest", or "over-mocking", so it does not reach the comprehensive synonym coverage of score 5.

4 / 5

Distinctiveness Conflict Risk

The niche (mocking best-practice verification in CI/test strategy review) is fairly distinct with specific triggers. Minor overlap risk remains with general code-review or CI-audit skills, and the garbled phrase "related to Follow mocking best practices" blurs the trigger wording slightly, keeping it below score 5.

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/mock-best-practices/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.