CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

laravel-patterns

Patrones de arquitectura Laravel, routing/controladores, Eloquent ORM, capas de servicio, colas, eventos, caché y API resources para aplicaciones en producción.

Quality

78%

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

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.

A highly actionable, code-rich Laravel pattern reference that assumes competence, but it functions as a monolithic catalog without progressive disclosure or a sequenced validation workflow.

Suggestions

Split the detailed pattern catalogs (Eloquent models, routing/binding rules, migrations) into one-level-deep reference files and link to them from SKILL.md to improve progressive disclosure.

Add a sequenced 'Cómo estructurar una feature' workflow with explicit validation checkpoints (e.g. run migrations, run tests, verify scoped bindings) for workflow clarity.

De-duplicate the repeated Project model examples by referencing a single canonical model definition.

DimensionReasoningScore

Conciseness

Mostly lean code with brief Spanish intros that assume Claude's competence, but the Project model is redefined across multiple sections, adding some redundancy that could be trimmed.

4 / 5

Actionability

Numerous complete, copy-paste-ready PHP examples (controllers/actions, route bindings, Eloquent casts, migrations, Form Requests, API resources) cover the common Laravel cases.

5 / 5

Workflow Clarity

This is a pattern catalog rather than a sequenced workflow; 'Cómo Funciona' lists loose principles but lacks explicit checkpoints or a validate-fix-retry feedback loop.

3 / 5

Progressive Disclosure

Section structure with headers is good, but all 410 lines are inlined in one file with no reference-file split for detailed catalogs (Eloquent, routing, migrations) that would aid navigation.

3 / 5

Total

15

/

20

Passed

Description

75%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 specific, well-scoped Laravel description with strong capability coverage, but it omits an explicit 'Use when...' trigger clause, capping its completeness.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when building or refactoring Laravel applications, working with Eloquent models, or designing queued/cache-backed APIs.'

Reframe domain nouns as concrete actions where possible (e.g. 'Structure controllers and services', 'Define Eloquent models with casts and scopes') to lift specificity.

Include a few more natural synonyms users say ('migrations', 'artisan', 'Form Requests') to broaden trigger coverage.

DimensionReasoningScore

Specificity

Lists several specific Laravel capabilities (routing/controladores, Eloquent ORM, capas de servicio, colas, eventos, caché, API resources) but as noun-phrase domains rather than concrete action verbs, so it sits at anchor 4 rather than 5.

4 / 5

Completeness

The 'what' is clear and detailed, but there is no 'Use when...' or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Natural terms a Laravel user would say ('Laravel', 'Eloquent ORM', 'colas', 'caché', 'API resources') are present with good coverage, though synonyms like 'artisan' or 'migrations' are missing.

4 / 5

Distinctiveness Conflict Risk

Tightly scoped to Laravel architecture with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

16

/

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-patterns/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.