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

80%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/laravel-patterns/SKILL.md

The canonical home for this skill is tdg-personal/laravel-patterns

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 thorough, highly actionable Laravel patterns reference with extensive executable code, but it is monolithic with no progressive disclosure to separate files and lacks validation checkpoints for its destructive/batch operations.

Suggestions

Add explicit validation/verification steps to destructive workflows: show checking migration state before/after `DB::transaction` and validating output, so workflow_clarity can exceed the cap of 3.

Split the detailed routing/binding and Eloquent pattern sections into separate reference files (e.g. `references/routing.md`, `references/eloquent.md`) and keep SKILL.md as a concise overview with one-level-deep links to improve progressive_disclosure.

De-duplicate the recurring `final class Project extends Model` examples by consolidating the model configuration, global scope, and query scope snippets into a single coherent example.

Dimension	Reasoning	Score
Conciseness	Mostly code-forward with terse directives and no padding of concepts Claude already knows, but the `final class Project extends Model` definition and scope patterns recur across three sections, a minor redundancy that could be tightened.	4 / 5
Actionability	Dozens of concrete, executable PHP blocks (routes, scoped bindings, models, form requests, migrations, transactions, query objects) cover the common Laravel cases copy-paste ready, exceeding anchor 4.	5 / 5
Workflow Clarity	'How It Works' gives a rough sequenced approach (controllers -> services -> models), but there are no validation/verification checkpoints, and destructive operations like DB::transaction and migrations lack validation feedback loops, capping the score at 3.	3 / 5
Progressive Disclosure	The body is well-organized with hierarchical headers, but it is a monolithic ~415-line file with no bundle files and no references to deeper files, so content that could be split (detailed routing/binding and Eloquent examples) is inlined.	3 / 5
	Total	15 / 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, specific description that explicitly answers both what the skill covers and when to use it, with a clear Laravel niche and low conflict risk. The only minor gaps are generic action verbs and a few missing natural synonyms.

Dimension	Reasoning	Score
Specificity	Lists seven concrete Laravel subsystems (routing/controllers, Eloquent ORM, service layers, queues, events, caching, API resources), but the action verbs ('building or reviewing') are generic while the specifics are domain nouns, sitting between anchor 4 and 5.	4 / 5
Completeness	Clearly states the 'what' (architecture patterns plus enumerated subsystems) and an explicit 'Use when building or reviewing Laravel apps — controllers, Eloquent, service layers, queues, or API resources' trigger clause, matching the anchor 5 example.	5 / 5
Trigger Term Quality	Natural terms like 'Laravel apps', 'controllers', 'Eloquent', 'service layers', 'queues', 'API resources' give good coverage, but common synonyms (Blade, Artisan, migrations, middleware, requests) are missing, matching anchor 4 rather than comprehensive anchor 5.	4 / 5
Distinctiveness Conflict Risk	Scoped to a Laravel-specific niche with concrete, domain-locked triggers, giving minimal overlap risk with other skills per anchor 5.	5 / 5
	Total	18 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: skills/laravel-patterns/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.