laravel-best-practices

Laravel framework skill for writing, reviewing, and testing PHP applications built with Laravel. Use whenever working on Laravel-specific patterns: controllers, FormRequests, Eloquent models, service/action classes, Blade templates, jobs, events, policies, observers, or Artisan commands. Also applies to Inertia frontends (React or Vue) embedded inside a Laravel project — covering useForm, usePage, Link navigation, partial reloads, page component naming (PostsIndexPage), and shadcn wrapper conventions. Trigger any time someone mentions Laravel, Eloquent, Artisan, Blade, FormRequest, Inertia within Laravel, N+1 queries in a Laravel app, inline controller validation, where business logic should live in a Laravel controller, or asks to follow best practices in a Laravel codebase. Does not apply to plain PHP scripts without Laravel, Rails, Django, standalone Next.js, or non-Laravel frameworks.

Quality

85%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

70%

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

This is a well-structured skill with clear workflows and good progressive disclosure through external references. The main weaknesses are moderate verbosity in the principles sections and lack of concrete code examples - the skill describes what to do but doesn't show executable Laravel/Inertia code snippets that Claude could directly use as templates.

Suggestions

Add 1-2 concrete code examples showing a thin controller + FormRequest + Service pattern to make the actionability more tangible

Include a complete JSON output example for the Review workflow rather than just describing the structure

Consolidate the Inertia React and Vue sections - they share significant overlap in directory structure and conventions that could be unified

Dimension	Reasoning	Score
Conciseness	The skill is reasonably efficient but includes some redundant explanations (e.g., restating principles that Laravel developers would know). The Inertia sections repeat structural information that could be consolidated, and some bullet points explain concepts Claude already understands.	2 / 3
Actionability	The skill provides structured workflows and references to external files (rulebook.json, inertia-react.md), but lacks concrete executable code examples. The JSON output format is described but not shown with a complete example. Instructions are procedural but abstract rather than copy-paste ready.	2 / 3
Workflow Clarity	The three workflows (Review, Generate code, Generate tests) are clearly sequenced with numbered steps. The review workflow includes explicit output requirements (rule_id, evidence, patch outline, test plan). Each workflow has a logical progression from analysis to output.	3 / 3
Progressive Disclosure	Excellent use of external references: rulebook.json as source of truth, separate markdown files for Inertia React/Vue details. The main skill provides high-level principles while pointing to one-level-deep references for detailed information. Navigation is clear with explicit file paths.	3 / 3
	Total	10 / 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.

This is an exemplary skill description that excels across all dimensions. It provides comprehensive coverage of Laravel-specific capabilities, includes natural trigger terms developers would use, explicitly states both what it does and when to use it, and clearly distinguishes itself from other framework skills through explicit exclusions.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions and patterns: 'controllers, FormRequests, Eloquent models, service/action classes, Blade templates, jobs, events, policies, observers, Artisan commands' plus detailed Inertia coverage including 'useForm, usePage, Link navigation, partial reloads, page component naming'.	3 / 3
Completeness	Clearly answers both what ('writing, reviewing, and testing PHP applications built with Laravel' with extensive pattern list) AND when ('Use whenever working on Laravel-specific patterns', 'Trigger any time someone mentions...'). Also includes explicit exclusions for clarity.	3 / 3
Trigger Term Quality	Excellent coverage of natural terms users would say: 'Laravel, Eloquent, Artisan, Blade, FormRequest, Inertia, N+1 queries, inline controller validation, business logic, best practices in a Laravel codebase'. These are terms developers naturally use when seeking Laravel help.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive with clear niche (Laravel framework specifically) and explicit exclusions ('Does not apply to plain PHP scripts without Laravel, Rails, Django, standalone Next.js, or non-Laravel frameworks') that prevent conflicts with other web framework skills.	3 / 3
	Total	12 / 12 Passed

Validation

81%

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 — 9 / 11 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	9 / 11 Passed

Repository: masterfermin02/laravel-agent-skill
Commit: 22c7c54

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