Name: testing-best-practices
Rating: 70.39999999999999 (1 reviews)
Author: yaojingang

testing-best-practices

Laravel test design and review. Use when selecting coverage, naming or structuring tests, choosing assertions or test data, isolating dependencies, testing HTTP or security boundaries, improving suite performance, or reviewing test value. Use framework guidance or search-docs for Pest and PHPUnit syntax.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

The canonical home for this skill is testing-best-practices in yaojingang/GEOFlow

Quality

Content

81%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-organized, lean skill body with a clear 5-step workflow containing validation and checklist checkpoints, and an excellent one-level-deep rule-index structure. Its gaps are the absence of worked examples and a time-sensitive version pin, plus the referenced rule files not being present in the provided bundle.

Suggestions

Add one or two short worked examples (e.g., a sample feature test and an assertion choice) to lift actionability toward fully executable guidance.

Move the 'PHPUnit 11.5.55' version pin into a documented/deprecated-style note so time-sensitive detail does not penalize conciseness.

Ensure the referenced rules/*.md files ship alongside SKILL.md so the Rule Index navigation resolves to real files.

Dimension	Reasoning	Score
Conciseness	Mostly lean and assumes Claude's competence without explaining basic testing concepts, but the time-sensitive 'PHPUnit 11.5.55' version pin and a few explanatory sentences ('A pattern repeated throughout the project is a convention…') could be trimmed, matching anchor-4 'efficient; minor instances of over-explanation' rather than the every-token-earns-its-place anchor 5.	4 / 5
Actionability	Concrete, specific instruction guidance ('Cover every changed decision… A decision is a branch, a validation, a calculation, or an authorization'; 'Run the smallest set of tests that covers the change') that is actionable for an instruction-only skill, but it lacks worked examples (no sample test or assertion), matching anchor-4 'mostly executable guidance with minor gaps' rather than anchor-5's copy-paste-ready examples.	4 / 5
Workflow Clarity	The 'How to Apply' section is a clear 5-step sequence with an explicit validation checkpoint ('The tests must pass') and a checklist ('Resolve every mismatch before completion'), matching anchor-5 'clear sequence with explicit validation steps and checklists'; test writing is not destructive/batch so no cap applies.	5 / 5
Progressive Disclosure	The overview plus a clean Rule Index table with one-level-deep, clearly signaled references is an anchor-5 structure, but verifying the references against the bundle shows the referenced rules/*.md files are not present, so navigation does not resolve to real files — a real gap that drops it to anchor-4 rather than the unclear-signaling anchor 3.	4 / 5
	Total	17 / 20 Passed

Description

92%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 with an explicit 'Use when' trigger clause covering a comprehensive range of concrete test-design actions and a clear Laravel-testing niche. Its only weakness is trigger-term naturalness: it leans on formal phrasing and omits common user synonyms like 'write a test' or 'unit/feature test'.

Suggestions

Add the most natural user trigger phrasings ('write a test', 'write unit/feature tests', 'mock dependencies') alongside the formal 'Use when' list.

Surface Pest and PHPUnit as triggers (not only as syntax-search targets) since users name those frameworks directly.

Dimension	Reasoning	Score
Specificity	Lists many concrete test-design actions (selecting coverage, naming/structuring tests, choosing assertions or test data, isolating dependencies, testing HTTP or security boundaries, improving suite performance, reviewing test value), giving comprehensive coverage beyond the anchor-4 'minor gaps' level.	5 / 5
Completeness	Clearly states the 'what' ('Laravel test design and review') and an explicit 'Use when…' clause with concrete trigger phrases, matching the anchor-5 'both what AND when with concrete triggers' and exceeding anchor-4's 'when could be more explicit'.	5 / 5
Trigger Term Quality	Good keyword coverage (naming tests, assertions, test data, suite performance, reviewing test value) but misses the most natural user phrasings like 'write a test', 'unit test', 'feature test', and 'mock'; Pest/PHPUnit appear only in the syntax-search clause rather than as triggers, so it falls short of comprehensive anchor-5 synonym coverage.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (Laravel test design and review) with test-scoped triggers, giving minimal conflict risk with other skills; matches anchor-5 'clear niche with distinct triggers'.	5 / 5
	Total	19 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
relative_links	Relative link issues: 9 missing	Warning

	Total	14 / 16 Passed

Repository: yaojingang/GEOFlow
Path: .claude/skills/testing-best-practices/SKILL.md
Commit: d7f601d

Reviewed: 8 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.