laravel-best-practices

Enforce Laravel best practices for code generation and review — SRP, skinny controllers, FormRequests, Policies, service/action classes, Eloquent, Blade safety, and Inertia conventions.

Quality

82%

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

Quality

Content

86%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 concise, well-structured, and actionable, with concrete Laravel primitives throughout and clean delegation to a related skill. The only gap is the lack of a complete executable code example, which keeps actionability just below 5.

Suggestions

Add one short copy-paste-ready example showing the recommended layering (e.g., a FormRequest + Service/Action + skinny controller skeleton) to lift actionability to 5.

Optionally sequence the review process as an explicit numbered workflow with a validation/checkpoint step (run tests after applying patch) to strengthen workflow clarity.

Dimension	Reasoning	Score
Conciseness	Lean and efficient throughout — compact tables encode rules, no padding, and no explaining of concepts Claude already knows; every token earns its place, matching the 'lean and efficient' anchor.	5 / 5
Actionability	Provides concrete executable guidance via real Laravel primitives ('->validated()', '$this->authorize()', 'config(key)', 'with()/load()', 'useForm', 'usePage<T>()', '<Link>'), but includes no complete copy-paste code example, leaving a minor gap below the 5 anchor.	4 / 5
Workflow Clarity	The review output format specifies per-finding fields (rule_id, evidence, recommendation, patch outline, test impact) as an implicit checklist, and test generation lists concrete coverage categories; this is a single-purpose enforcement skill with no destructive batch step requiring a validation cap, so it sits just below the explicit-sequence/checkpoint anchor of 5.	4 / 5
Progressive Disclosure	Under 50 lines with no bundle files; content is well-organized into clear sections (When to use, Key backend rules, Key Inertia rules, Review output format, Test generation) and correctly delegates Inertia detail to the separate 'inertia-development' skill, satisfying the simple-skill exception for a 5.	5 / 5
	Total	18 / 20 Passed

Description

70%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 niche, with strong trigger-term coverage. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which caps completeness at 3.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when implementing or refactoring Laravel controllers, FormRequests, services, or reviewing Laravel code/diffs') to satisfy the completeness rubric.

Frame capabilities as discrete actions rather than a topic list to lift specificity toward 5.

Include a couple of natural user phrasings or synonyms users would actually say (e.g., 'Laravel code review', 'refactoring Laravel apps') to push trigger-term quality higher.

Dimension	Reasoning	Score
Specificity	Lists several concrete enforcement domains ('SRP, skinny controllers, FormRequests, Policies, service/action classes, Eloquent, Blade safety, and Inertia conventions') with minor framing gaps — topics rather than discrete actions, so not a 5.	4 / 5
Completeness	The 'what' is clear and detailed ('Enforce Laravel best practices for code generation and review — ...'), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Strong Laravel-specific keyword coverage (FormRequests, Eloquent, Blade, Inertia, Policies, service/action classes) with good synonym spread, but lacks a natural 'Use when...' trigger phrase and file-extension-style triggers, keeping it below 5.	4 / 5
Distinctiveness Conflict Risk	A clear Laravel-specific niche with distinct framework-level triggers; it is highly unlikely to fire for unrelated skills, matching the 'clear niche with distinct triggers; minimal conflict risk' anchor.	5 / 5
	Total	16 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: masterfermin02/laravel-agent-skill
Path: resources/boost/skills/laravel-best-practices/SKILL.md
Commit: 22c7c54

Reviewed: 7 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.