CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

laravel-tdd

Test-driven development for Laravel with PHPUnit and Pest, factories, database testing, fakes, and coverage targets.

Quality

75%

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/laravel-tdd/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 complete, executable PHP examples across testing layers and strong organization. Its main weakness is redundancy — repeated RefreshDatabase guidance and overlapping example pairs — that could be tightened without losing value.

Suggestions

Delete the paragraph after the Database Strategy bullets (it restates RefreshDatabase/DatabaseTransactions behavior almost verbatim) and drop the redundant 'Database Testing' section.

Consolidate the four full test-class examples: keep one PHPUnit and one Pest example, and note that Pest mirrors PHPUnit syntax, or move the extended examples (Inertia, persistence) into a references/ file.

DimensionReasoningScore

Conciseness

Mostly efficient terse bullets and code, but the 'Use RefreshDatabase as the default...' paragraph nearly verbatim repeats the Database Strategy bullets, the 'Database Testing' section re-covers that ground, and four full test-class examples pad the length. This is more than minor trimming, so it sits at anchor 3 rather than 4.

3 / 5

Actionability

Fully executable, copy-paste-ready examples with imports cover the common cases: HTTP create/index tests in both PHPUnit and Pest, persistence, factory states, Queue/Notification fakes, Sanctum, Gate assertions, and Inertia props — plus concrete commands ('php artisan test', 'vendor/bin/pest') and phpunit.xml configuration guidance.

5 / 5

Workflow Clarity

The Red-Green-Refactor cycle is a clear, inherently looping sequence, and test commands and coverage targets are given. Not 5 because per-phase validation is implicit ('Write a failing test', 'keeping tests green') rather than explicit run/verify steps; not 3 because the feedback loop and commands are clearly stated.

4 / 5

Progressive Disclosure

Single-file skill with no bundle files; sections are well-organized with clear headers and the content is easy to navigate. Not 5 because the ~280-line body inlines four complete test classes that could be split into reference files for a leaner overview; not 3 because the structure is genuinely good.

4 / 5

Total

16

/

20

Passed

Description

66%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 and distinctive, naming the domain, frameworks, and concrete testing capabilities, but it omits any 'when to use' guidance. Adding an explicit trigger clause would lift completeness and make invocation conditions clear.

Suggestions

Append a trigger clause such as: 'Use when writing or running tests in Laravel apps, practicing TDD, or when the user mentions PHPUnit, Pest, factories, fakes, or coverage.'

Include natural trigger variations users would say, e.g. 'unit tests', 'feature tests', 'increasing test coverage'.

Optionally mention HTTP/endpoint and auth testing to round out the capability list toward comprehensive coverage.

DimensionReasoningScore

Specificity

Lists several concrete capabilities ('Test-driven development', 'factories', 'database testing', 'fakes', 'coverage targets') alongside the frameworks, matching the 'several specific actions; minor gaps' anchor. Not 5 because coverage is not comprehensive — feature/HTTP endpoint testing and auth testing from the body are absent.

4 / 5

Completeness

Has a clear 'what' (TDD for Laravel with PHPUnit/Pest, factories, database testing, fakes, coverage targets) but no 'Use when...' clause or equivalent explicit trigger guidance, capping it at the anchor-3 level. Not 4 because nothing about 'when' is explicit or even weakly implied.

3 / 5

Trigger Term Quality

Terms like 'Test-driven development', 'Laravel', 'PHPUnit', 'Pest', and 'coverage' are natural phrases a user would say when needing this skill. Not 5 because common variations like 'testing', 'unit tests', 'feature tests', or 'write tests' are missing.

4 / 5

Distinctiveness Conflict Risk

Clear niche (Laravel testing with PHPUnit/Pest) with mostly distinct triggers. Not 5 because a generic PHP-testing or TDD skill would have minor overlap with these triggers.

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

valeriibeck-star/claude-skills

Path

skills/laravel-tdd/SKILL.md

Revision

0bda8b8

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill