Tessl • The management layer for AI agent skills

SkillPublic

laravel-patterns

Laravel architecture patterns, routing/controllers, Eloquent ORM, service layers, queues, events, caching, and API resources for production apps.

Quality

71%

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 laravel-patterns in affaan-m/ECC

Quality

Content

65%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 delivers substantial executable, Laravel-specific code with lean commentary and good topical organization. Its main weaknesses are the absence of any validation or verification guidance in the workflows and the monolithic single-file structure, where 400 lines of pattern reference would benefit from split reference files.

Suggestions

Split large topical sections (Eloquent patterns, routing/binding, queues/events/caching) into reference files under references/ and keep SKILL.md as a concise overview with clearly signaled links — this directly improves progressive_disclosure.

Add validation checkpoints to the transactional and batch patterns, e.g. verify model state after DB::transaction or wrap queued jobs with failure/retry handling, to lift workflow_clarity.

Remove the duplicated ProjectStatus cast snippet and either add code to the Events/Jobs/Queues and Caching bullet sections or move them to a reference file.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean directives plus code with no basic-concept explanations, but has minor trimmable redundancy: the ProjectStatus cast appears in both the model example and the Custom Casts section, and the one-sentence "Project Structure" section is immediately followed by another heading. This fits anchor 4 (efficient with minor over-explanation) rather than 5.	4 / 5
Actionability	Most guidance is concrete, executable PHP (actions, scoped route bindings, service provider bindings, migrations, form requests, transactions), matching anchor 4. It falls short of 5 because the budgetCents() Attribute and $casts snippets are fragments without class context, and the Events/Jobs/Queues and Caching sections are bullet points with no code.	4 / 5
Workflow Clarity	The layering guidance (controllers -> services/actions -> models) implies a sequence, but the skill presents patterns as a catalog rather than a sequenced workflow, with no validation checkpoints, testing steps, or error-recovery loops for risky operations like multi-step DB updates. Anchor 3 (sequence present but checkpoints missing or implicit) fits; the batch/destructive cap also applies.	3 / 5
Progressive Disclosure	Sections are well-organized with clear headers, but the entire ~400-line pattern reference is inlined in SKILL.md with zero bundle files; topics like Eloquent patterns, routing, and queues/caching clearly could be split into separate reference files. This matches anchor 3 (content that should be separate is inline) better than 2, since structure is present.	3 / 5
	Total	14 / 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 names a clear, well-scoped Laravel niche with specific coverage areas and strong domain keywords, but it is a topic list rather than an action-oriented capability statement and entirely lacks a 'Use when...' trigger clause. Adding explicit usage triggers and reframing topics as concrete actions would raise both completeness and specificity.

Suggestions

Add an explicit trigger clause, e.g. "Use when building or refactoring Laravel applications or APIs, working with Eloquent models, or designing controller/service layers" — this addresses the completeness cap.

Reframe the topic nouns as concrete actions (e.g., "Structure controllers and service layers, define Eloquent models and scopes, design queued jobs and events") to strengthen specificity.

Include a few more natural trigger terms users say, such as migrations, Blade, middleware, or artisan, to improve keyword coverage.

Dimension	Reasoning	Score
Specificity	Lists seven specific coverage areas ("routing/controllers, Eloquent ORM, service layers, queues, events, caching, and API resources") but as topic nouns rather than concrete action verbs like the anchor-5 example, so it fits anchor 4 (several specific items, minor gaps) rather than 5.	4 / 5
Completeness	The 'what' is clear and specific (patterns across seven named Laravel areas for production apps), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines; it is not 2 because the 'what' is not vague.	3 / 5
Trigger Term Quality	Includes natural terms users say for this domain ("Laravel", "Eloquent", "controllers", "routing", "queues", "API resources"), but common variations like migrations, Blade, artisan, or middleware are missing, matching anchor 4 rather than 5.	4 / 5
Distinctiveness Conflict Risk	"Laravel", "Eloquent ORM", and "API resources" establish a clear niche, but generic terms like "caching", "events", and "queues" create minor overlap risk with closely related backend/caching skills, fitting anchor 4 better than 5.	4 / 5
	Total	15 / 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
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-patterns/SKILL.md
Revision: 0bda8b8

Reviewed: 2 days ago

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.

laravel-patterns

Table of Contents

Is this your skill?