CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

laravel-tdd

Desarrollo guiado por pruebas para Laravel con PHPUnit y Pest, factories, pruebas de base de datos, fakes y objetivos de cobertura.

Quality

70%

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

Quality

Content

71%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 comprehensive executable examples and a clear TDD workflow, but it carries redundant prose and would benefit from moving detailed examples into reference files for better progressive disclosure.

Suggestions

Remove the duplicated RefreshDatabase/DatabaseTransactions explanation that restates the preceding bullet list.

Extract the longer code examples (factories, fakes, Sanctum, Inertia) into a references/ file and link to it from the body.

Add an explicit feedback-loop checklist for the red-green-refactor cycle (run tests → fix → re-run until green).

DimensionReasoningScore

Conciseness

Most sections are efficient and example-driven, but the 'Estrategia de Base de Datos' section duplicates the RefreshDatabase/DatabaseTransactions explanation almost verbatim in prose right after the bullet list, adding padding that could be trimmed.

3 / 5

Actionability

Multiple copy-paste-ready, executable PHP examples cover the common cases (PHPUnit, Pest, factories, fakes, Sanctum, Inertia), with specific assertions and commands throughout.

5 / 5

Workflow Clarity

The red-green-refactor cycle and test-layer guidance give a clear sequence with mostly-present checkpoints, though explicit validation/feedback loops (e.g. run tests, fix, re-run until green) are implied rather than spelled out as a checklist.

4 / 5

Progressive Disclosure

Content is well-sectioned but entirely self-contained with no bundle files present; much of the duplicated example and reference material could live in separate reference files, so structure is adequate but not optimally split.

3 / 5

Total

15

/

20

Passed

Description

57%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 clearly distinct within the Laravel testing niche, but it lacks an explicit 'Use when...' trigger clause, capping its completeness and leaving its trigger-term coverage short of natural user phrasings.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Úsalo al crear o corregir funcionalidades Laravel, o cuando el usuario pida pruebas, cobertura o TDD.'

Broaden trigger terms with natural user phrasings and synonyms: 'pruebas', 'test', 'probar', 'cobertura de código', 'TDD'.

Keep the third-person voice but ensure the 'what' and 'when' are both concrete and explicit in a single sentence.

DimensionReasoningScore

Specificity

Lists several concrete actions across the domain — 'factories, pruebas de base de datos, fakes y objetivos de cobertura' alongside PHPUnit/Pest — giving specific capabilities, though it stops short of enumerating the full breadth of TDD activities.

4 / 5

Completeness

It clearly answers 'what' the skill does, but there is no 'Use when...' clause or equivalent explicit 'when' trigger guidance, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Relevant domain terms (Laravel, PHPUnit, Pest, factories, cobertura) are present, but it omits natural user phrasings and synonyms like 'tests', 'probar', 'cobertura de código', or 'desarrollo guiado por pruebas' as a standalone trigger a user might say.

3 / 5

Distinctiveness Conflict Risk

The Laravel + PHPUnit + Pest framing carves a clear niche distinct from generic testing skills, with only minor overlap risk against a broader PHP-testing skill.

4 / 5

Total

14

/

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

affaan-m/ECC

Path

docs/es/skills/laravel-tdd/SKILL.md

Reviewed

Table of Contents

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.