laravel-tdd

Laravel testing strategies with PHPUnit, Pest, model factories, HTTP tests, Sanctum authentication testing, mocking, and coverage. Use when writing Laravel tests with PHPUnit or Pest, or driving a Laravel feature test-first.

Quality

82%

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

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.

The body is highly actionable with executable code across the full Laravel testing surface, but the TDD workflow lacks explicit validation checkpoints and a large reference surface is inlined rather than split into bundle files.

Suggestions

Make the Red-Green-Refactor cycle an explicit checkpointed sequence — e.g. '1. Run test → see it fail (RED) 2. Implement until green 3. Run full suite 4. Refactor only while green' — with an error-recovery loop.

Move the bulk reference material (factory definitions, the full HTTP/API/Sanctum test classes, the fakes catalog) into references/ files (e.g. factories.md, http-testing.md, mocking.md) and link to them one level deep.

Trim duplicated auth/authorization test classes and the verbose factory definitions to reduce token weight while keeping representative examples.

Dimension	Reasoning	Score
Conciseness	The body is efficient and avoids explaining concepts Claude already knows, with code as the payload and minimal useful comments, but a few sections (full factory definitions, repeated auth test classes) could be trimmed.	4 / 5
Actionability	Provides fully executable, copy-paste-ready code throughout — PHPUnit config, factories, model/HTTP/API/Sanctum tests, fakes, artisan tests, and Pest — covering the common cases concretely.	5 / 5
Workflow Clarity	The Red-Green-Refactor cycle names the sequence but the validate-then-proceed checkpoints are only implicit in code comments rather than an explicit checkpoint sequence with error-recovery feedback loops.	3 / 5
Progressive Disclosure	Content is well-organized with clear section headers and a quick-reference table, but substantial reference material (full factories, multiple complete test classes) is inlined in SKILL.md with no bundle files to offload it.	3 / 5
	Total	15 / 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.

The description is specific, third-person, and clearly answers both what the skill does and when to use it with concrete trigger phrases. Minor headroom only on trigger-term synonym coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — 'PHPUnit, Pest, model factories, HTTP tests, Sanctum authentication testing, mocking, and coverage' — giving comprehensive coverage of Laravel testing, matching the anchor for multiple specific concrete actions.	5 / 5
Completeness	Explicitly answers both 'what' (the listed testing strategies) and 'when' (a concrete 'Use when...' trigger clause with multiple trigger phrases).	5 / 5
Trigger Term Quality	Natural terms like 'writing Laravel tests with PHPUnit or Pest' and 'driving a Laravel feature test-first' are present, but a few common synonyms/extensions are missing, so it sits just below comprehensive coverage.	4 / 5
Distinctiveness Conflict Risk	The Laravel-TDD niche with distinct triggers (PHPUnit/Pest, feature test-first) creates a clear niche with minimal conflict risk against other skills.	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
skill_md_line_count	SKILL.md is long (676 lines); consider splitting into references/ and linking	Warning
metadata_version	'metadata.version' is missing	Warning

	Total	14 / 16 Passed

Repository: affaan-m/ECC
Path: skills/laravel-tdd/SKILL.md
Commit: 06c5e11

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