Name: laravel-best-practices
Rating: 87.2 (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.04x

Quality

89%

Does it follow best practices?

Impact

76%

1.04x

Average score across 3 eval scenarios

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 a well-organized, token-efficient index that delegates detail to per-concern rule files and includes a clear application workflow with validation checkpoints. The main gap is that the referenced rule files are not present in the bundle, so the deep actionability and any error-recovery feedback loops cannot be verified from SKILL.md alone.

Suggestions

Add an explicit feedback loop to the How to Apply workflow (e.g., 'If formatting/static-analysis or tests fail, fix and re-run before proceeding') to reach full workflow-clarity maturity.

Ensure the referenced rules/*.md files are bundled alongside SKILL.md so the one-level-deep progressive disclosure is actually verifiable and the deferred rule content is available.

Surface 1-2 concrete code patterns inline (e.g., an eager-loading example for N+1) so the most common cases are actionable without opening a rule file.

Dimension	Reasoning	Score
Conciseness	The body is lean with no padding or explanation of concepts Claude already knows (no 'what is Laravel/Eloquent' filler); the Consistency First principle, How to Apply steps, rule index, and decision rules each earn their place, matching the lean-and-efficient anchor.	5 / 5
Actionability	Provides concrete executable guidance ('Map every affected concern to the rule index below. Read each mapped rule file before editing', 'Verify version-sensitive Laravel APIs... with search-docs', 'Run the narrowest relevant tests first'), but the substantive rule content lives in the referenced rule files rather than inline, so it is mostly rather than fully executable here.	4 / 5
Workflow Clarity	The How to Apply section is a clear 6-step sequence with checkpoints (verify version-sensitive APIs, run narrowest tests then formatting/static-analysis, re-read the diff against mapped rules), but it lacks an explicit fail->fix->retry feedback loop, fitting the clear-sequence-with-minor-validation-gaps anchor rather than the full-feedback-loop one.	4 / 5
Progressive Disclosure	SKILL.md is a clean overview/index pointing one level deep to 18 rule files plus an external testing skill via a concern->file table with clear navigation; no bundle was provided to verify against, but the structure as written matches the canonical well-signaled one-level-deep reference pattern.	5 / 5
	Total	18 / 20 Passed

Description

92%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 comprehensive and well-structured, clearly stating both capabilities and explicit trigger conditions in third-person voice with minimal conflict risk. Its only weak spot is trigger-term breadth, where a few natural synonyms and the .php extension are absent.

Dimension	Reasoning	Score
Specificity	Lists many concrete actions and targets across Laravel domains ('creating or modifying controllers, models, migrations, form requests, policies, jobs... Eloquent queries' plus 'N+1 and query performance issues, caching strategies, authorization and security patterns, validation, error handling, queue and job configuration, route definitions'), matching the comprehensive-coverage anchor.	5 / 5
Completeness	Explicitly answers both what ('creating or modifying controllers, models... Eloquent queries') and when via multiple concrete trigger clauses ('Apply this skill whenever writing, reviewing, or refactoring Laravel PHP code', 'Triggers for...', 'Also use for Laravel code reviews'), matching the anchor that requires both with concrete trigger phrases.	5 / 5
Trigger Term Quality	Strong natural keyword coverage (Laravel, Eloquent, N+1, migrations, caching, validation, queues, routes, code reviews, refactoring) but missing common synonyms/extensions a user might say such as 'artisan', 'Blade', or '.php', fitting the good-coverage-with-few-gaps anchor rather than the comprehensive one.	4 / 5
Distinctiveness Conflict Risk	Scoped to 'Laravel PHP code' with framework-specific triggers (Eloquent, form requests, policies, migrations) giving a clear niche and minimal conflict risk; testing is explicitly deferred to a separate skill in the body, reinforcing distinctiveness.	5 / 5
	Total	19 / 20 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: 19 missing	Warning

	Total	14 / 16 Passed

Repository: laravel/boost
Path: .ai/laravel/skill/laravel-best-practices/SKILL.md
Commit: 5b33d49

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.