CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

laravel-patterns

Laravel architecture patterns, routing/controllers, Eloquent ORM, service layers, queues, events, caching, and API resources for production apps. Use when building or reviewing Laravel apps — controllers, Eloquent, service layers, queues, or API resources.

Quality

77%

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

Quality

Content

57%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, code-rich pattern catalog with strong actionability, held back by duplication (the same Eloquent filter shown three ways, repeated response-envelope examples), the absence of any validation checkpoints, and a monolithic single-file structure with no progressive disclosure. It reads as a solid reference but would benefit from trimming and splitting.

Suggestions

Consolidate the three sections demonstrating the same whereNull('archived_at') filter (scopeActive, global scopes, ProjectQuery::active) into one section showing when to prefer each approach.

Split the detailed pattern catalogs (routing/nesting examples, Eloquent variants, migrations) into references/ files and keep SKILL.md as a lean overview with clearly signaled links.

Add verification guidance for risky operations, e.g. run migrations with a rollback plan, wrap transactional updates with a check that the operation succeeded, or run php artisan test after changes.

DimensionReasoningScore

Conciseness

Mostly lean and code-heavy, but the same filter is demonstrated three redundant ways (scopeActive, a global scope, and ProjectQuery::active all use whereNull('archived_at')), the response-envelope JSON pattern repeats, and 'Project Structure'/'Recommended Layout' headings are redundant.

3 / 5

Actionability

Concrete, mostly copy-paste-ready PHP across controllers, routes, models, migrations, form requests, and resources; minor gaps remain in fragmentary snippets (budgetCents attribute, bare $casts) and undefined supporting classes (CreateOrderData, OrderRepository).

4 / 5

Workflow Clarity

Topics are sequenced sensibly (structure, layers, routing, models, migrations, validation, API), but no validation checkpoints exist anywhere; the transactions section prescribes multi-step DB updates with no verify step, and the skill is far too long for the simple-skill exception.

3 / 5

Progressive Disclosure

Well-sectioned with clear headers, but everything is inlined in a single ~415-line SKILL.md with no references/ files, so detailed pattern catalogs that belong in separate files are inline rather than pointed to.

3 / 5

Total

13

/

20

Passed

Description

87%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 description that states concrete capability areas and pairs them with an explicit, trigger-rich 'Use when...' clause. It falls just short of top marks on specificity and trigger terms because the capabilities are listed as topics rather than actions and a few natural Laravel terms (migrations, Blade, artisan) are absent.

DimensionReasoningScore

Specificity

Names several specific capability areas ('routing/controllers, Eloquent ORM, service layers, queues, events, caching, and API resources'), but these are topic nouns rather than concrete action verbs and coverage has minor gaps (migrations, validation, testing are not named).

4 / 5

Completeness

Explicitly answers both what ('Laravel architecture patterns... for production apps') and when ('Use when building or reviewing Laravel apps — controllers, Eloquent, service layers, queues, or API resources') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural keyword coverage ('Laravel apps', 'Eloquent', 'controllers', 'service layers', 'queues'), but a few common terms users would say are missing (e.g., 'migrations', 'Blade', 'artisan').

4 / 5

Distinctiveness Conflict Risk

Clear niche (Laravel specifically) with distinct framework-specific triggers; minimal risk of triggering for the wrong skill.

5 / 5

Total

18

/

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

affaan-m/ECC

Path

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.