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

74%

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

65%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 and lean, with excellent progressive disclosure pointing to a real references file. Its weaknesses are vague, non-executable Check/Fix/Code Review sections and missing validation checkpoints in the review workflow.

Suggestions

Replace the abstract Check/Fix directives with concrete, executable review steps (e.g., specific grep patterns or commands to detect missing afterEach cleanup and over-mocking).

Add an explicit validation/verification checkpoint to the Code Review workflow, such as 'run the test suite and confirm a mocked-out assertion fails when the rule is violated, then verify CI blocks the regression'.

Inline one or two short representative code examples (a good vs. bad mock cleanup snippet) so the body is actionable without requiring the references file for common cases.

Dimension	Reasoning	Score
Conciseness	The body is lean with terse Quick Reference bullets and short mode sections; only the opening sentence restates a concept Claude already knows, so it is efficient with minor trimmable over-explanation.	4 / 5
Actionability	The Quick Reference offers some concrete guidance (jest.restoreAllMocks() in afterEach, use MSW), but the Check/Fix/Explain/Code Review sections give high-level direction ('review...', 'improve mocking strategy by...') rather than executable steps, with the concrete detail delegated to references.	3 / 5
Workflow Clarity	Check/Fix/Explain/Code Review act as a loose framework with an implied review-then-fix sequence, but there are no explicit validation checkpoints or feedback loops in the body.	3 / 5
Progressive Disclosure	A clear overview with a single well-signaled one-level-deep reference to references/rule.md (verified to exist) for full details, with content appropriately split and easy navigation.	5 / 5
	Total	15 / 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 well-constructed description with an explicit 'Use when' trigger, concrete review actions, and a clear focus directive on continuous verification. It is distinct and complete, with only minor keyword-coverage and overlap gaps.

Dimension	Reasoning	Score
Specificity	Names the domain (CI coverage, automated checks, test strategy for mocking) and several concrete review actions ('reviewing CI coverage', 'Focus on whether the rule is continuously verified'), with only minor coverage gaps.	4 / 5
Completeness	Explicitly answers both what (reviewing CI coverage/automated checks/test strategy for mocking) and when ('Use when reviewing CI coverage, automated checks, or test strategy related to...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural phrases users would say ('CI coverage', 'automated checks', 'test strategy', 'mocking best practices') with good coverage, though a few synonyms are missing.	4 / 5
Distinctiveness Conflict Risk	Scoped to mocking best practices review with mostly distinct triggers, though 'CI coverage, automated checks, test strategy' could overlap with other testing-review skills.	4 / 5
	Total	17 / 20 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: 30756a7

Reviewed: 5 days 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.