Name: laravel-best-practices
Rating: 92.6 (1 reviews)
Author: laravel

laravel-best-practices

Apply this skill whenever writing, reviewing, or refactoring Laravel PHP code. This includes creating or modifying controllers, models, migrations, form requests, policies, jobs, scheduled commands, service classes, and Eloquent queries. Triggers for N+1 and query performance issues, caching strategies, authorization and security patterns, validation, error handling, queue and job configuration, route definitions, and architectural decisions. Also use for Laravel code reviews and refactoring existing Laravel code to follow best practices. Covers any task involving Laravel backend PHP code patterns.

1.23x

Quality

96%

Does it follow best practices?

Impact

83%

1.23x

Average score across 3 eval scenarios

Securityby

High

Do not use without reviewing

Quality

Content

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A lean, well-organized index skill with concrete process steps and explicit verification checkpoints. Its one weakness is progressive disclosure: the Rule Index links to 20 rule files that are missing from the bundle, so the promised detailed material is unreachable.

Suggestions

Ship the referenced rules/*.md rule files in the bundle (rules/db-performance.md, rules/eloquent.md, rules/security.md, etc.) — the Rule Index currently links to 20 files that do not exist, leaving progressive disclosure as dead ends.

If some rule files are not yet written, mark them as TODO or remove their rows from the Rule Index so every link in the table resolves to a real file.

Make the step-5/6 verification a true feedback loop by stating the retry path, e.g. 'if tests or static-analysis fail, fix and re-run them before finishing', which would also strengthen workflow_clarity's error-recovery angle.

Dimension	Reasoning	Score
Conciseness	Lean ~50-line body that never explains concepts Claude already knows (no 'what is Laravel/Eloquent'); every section — Consistency First, How to Apply, Rule Index, Decision Rules — adds actionable guidance, so every token earns its place.	3 / 3
Actionability	Concrete process guidance rather than vague direction: 'Map every affected concern to the rule index', 'Verify version-sensitive Laravel APIs... with search-docs', 'Run the narrowest relevant tests first, then... formatting and static-analysis checks'. As an instruction/index skill, absence of inline code is acceptable per the scoring notes since the guidance is specific and actionable.	3 / 3
Workflow Clarity	The six-step 'How to Apply' is a clear sequence with explicit verification checkpoints — verify APIs against the installed version (step 4), run narrow tests plus formatting/static-analysis (step 5), and re-read the diff against every mapped rule (step 6) — matching the 'clear sequence with explicit validation steps' anchor.	3 / 3
Progressive Disclosure	The SKILL.md is a well-signaled one-level-deep index (a concern→file table linking 20 rule files), but the referenced rules/*.md files do not exist in the bundle — no rules/, references/, scripts/, or assets/ directory is present — so the disclosure structure is not actually realized and navigation leads to dead ends.	2 / 3
	Total	11 / 12 Passed

Description

100%

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 with explicit trigger guidance and a clearly distinct Laravel niche. It is somewhat long and the two enumerated lists overlap, but every part is concrete and earns its place.

Dimension	Reasoning	Score
Specificity	Lists many concrete action targets — 'controllers, models, migrations, form requests, policies, jobs, scheduled commands, service classes, and Eloquent queries' — matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicitly answers both what ('creating or modifying controllers, models, migrations...') and when ('Apply this skill whenever writing, reviewing, or refactoring Laravel PHP code', 'Also use for Laravel code reviews'), so the 'Use when...' trigger is present and completeness is not capped at 2.	3 / 3
Trigger Term Quality	Covers natural terms a Laravel user would actually say — 'writing, reviewing, or refactoring Laravel PHP code', 'N+1', 'caching', 'authorization', 'validation', 'code reviews' — with good variation rather than jargon-only phrasing.	3 / 3
Distinctiveness Conflict Risk	Scoped tightly to 'Laravel PHP code' / 'Laravel backend PHP code patterns', a clear niche with distinct triggers unlikely to fire for non-Laravel or non-PHP skills.	3 / 3
	Total	12 / 12 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
relative_links	Relative link issues: 20 missing	Warning

	Total	14 / 16 Passed

Repository: laravel/boost
Path: .ai/laravel/skill/laravel-best-practices/SKILL.md
Commit: 21009e9

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