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

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/mock-best-practices/SKILL.md

Quality

Content

57%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill uses progressive disclosure well, offloading code and detail to a real reference file, but the body's instructional sections are abstract descriptions rather than concrete, executable guidance and lack validation checkpoints.

Suggestions

Replace the conceptual opening sentence with a terse purpose line, or move the rationale into rule.md, to stop re-explaining what mocking is.

Make Check/Fix/Code Review actionable with concrete steps or a short inline example (e.g., grep for jest.mock without a matching afterEach(restoreAllMocks), then flag the file), instead of describing the task.

Add an explicit validation checkpoint in the Code Review workflow (e.g., confirm the CI step fails when the mock rule is violated, and re-run until it blocks the regression).

Dimension	Reasoning	Score
Conciseness	The body is mostly lean, but the opening sentence explaining what mocking is and why over-mocking is risky covers a concept Claude already knows and could be cut.	2 / 3
Actionability	Quick Reference offers a few concrete directives (jest.restoreAllMocks() in afterEach, use MSW), but the Check/Fix/Explain sections describe tasks abstractly ('Review this test file...', 'Improve mocking strategy by...') with no executable code in the body.	2 / 3
Workflow Clarity	Check, Fix, Explain, and Code Review form a loose sequence but there are no explicit validation checkpoints or feedback loops, and CI/batch verification contexts are capped at 2 without them.	2 / 3
Progressive Disclosure	A well-organized overview points via a clearly signaled, one-level-deep reference to references/rule.md (verified to exist and hold the code examples and details), splitting content appropriately.	3 / 3
	Total	9 / 12 Passed

Description

67%

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 trigger clause and answers both what and when, but its action list is narrow, its trigger phrasing is partly awkward/jargon-laden, and it risks overlap with similar rule-review skills.

Suggestions

Reword the embedded rule title into natural user phrasing (e.g., 'Use when reviewing test or CI coverage for mocking practices') and drop internal jargon like 'continuously verified' or pair it with a plainer term.

Add one or two concrete actions beyond 'reviewing' (e.g., 'audit mock cleanup, flag over-mocking, verify CI blocks regressions') to lift specificity.

Differentiate the trigger from sibling rule skills by foregrounding the mocking-specific cues ('mock cleanup', 'over-mocking', 'jest.restoreAllMocks') rather than the generic CI/test-strategy terms.

Dimension	Reasoning	Score
Specificity	Names the domain ('CI coverage, automated checks, or test strategy') and a primary action ('reviewing') plus a focus qualifier, but does not list multiple distinct concrete actions as the top anchor requires.	2 / 3
Completeness	An explicit 'Use when...' trigger clause is present and the description answers both what (review/focus on continuous verification of the rule) and when, so it is not capped at 2.	3 / 3
Trigger Term Quality	Includes relevant natural terms (CI coverage, automated checks, test strategy, mocking) but the embedded rule title 'Follow mocking best practices' reads awkwardly and 'continuously verified' is internal jargon, leaving common variations uncovered.	2 / 3
Distinctiveness Conflict Risk	The 'mocking best practices' niche is fairly specific, but the generic CI/test-strategy trigger terms would overlap with sibling frontendchecklist rule-review skills.	2 / 3
	Total	9 / 12 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: thedaviddias/Front-End-Checklist
Path: skills/mock-best-practices/SKILL.md
Commit: 48405aa

Reviewed: about 10 hours ago

Table of Contents

Discovery Implementation Validation

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.