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.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Quality

Content

78%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.

A well-architected, token-efficient quick reference that consistently names specific Laravel APIs rather than hand-waving. Its main weakness is that the detailed rule files it points to are missing from the provided bundle, leaving the progressive-disclosure layer non-functional, and the body itself lacks executable code examples.

Suggestions

Ship (or confirm the presence of) the `rules/*.md` bundle files — the body references 19+ rule files that are absent from the provided bundle, so every "→ rules/x.md" link currently leads nowhere.

Add at least one short executable code snippet per section (or ensure each rule file opens with one) so the guidance is copy-paste ready rather than directive-only.

Add an explicit validation checkpoint in "How to Apply" for refactoring/migration work (e.g. "run the test suite and `php artisan migrate:fresh` in a scratch DB before committing") since the skill governs destructive changes like irreversible migrations.

Dimension	Reasoning	Score
Conciseness	Lean one-line bullets that teach what-to-do and why with no concept padding or restating of basics Claude already knows; every line carries a specific directive, e.g. "Eager load with `with()` to prevent N+1 queries".	5 / 5
Actionability	Every bullet names a concrete API or pattern (e.g. `Model::preventLazyLoading()`, `Cache::flexible()`, backoff `[1, 5, 10]`), but the body contains no executable code blocks — the runnable detail is deferred to the per-section rule files, so guidance is actionable yet incomplete on its own.	4 / 5
Workflow Clarity	The "How to Apply" section sequences identify-file-type → check-sibling-patterns (Consistency First) → verify-syntax-with-`search-docs`, with a verification checkpoint in step 3; minor gaps remain around post-refactor test validation.	4 / 5
Progressive Disclosure	Structure and signaling are strong — 19 cleanly sectioned topics each pointing to a `rules/*.md` file — but the referenced rule files are not present in the bundle, so the one-level-deep navigation the overview promises does not resolve.	3 / 5
	Total	16 / 20 Passed

Description

100%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.

An exemplary description: concrete, comprehensive, third-person, with explicit trigger guidance covering both what the skill does and when to invoke it. It distinguishes itself clearly within the Laravel niche.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions ("writing, reviewing, or refactoring"; "creating or modifying controllers, models, migrations, form requests, policies, jobs, scheduled commands, service classes, and Eloquent queries") with comprehensive coverage of the Laravel backend domain.	5 / 5
Completeness	Explicitly answers both "what" (enumerated code artifacts and operations) and "when" ("Apply this skill whenever...", "Triggers for...", "Also use for...") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural keywords a Laravel developer would actually say — "N+1", "query performance", "caching", "authorization and security", "validation", "queue and job configuration", "Laravel code reviews", "refactoring" — including synonyms and common phrasings.	5 / 5
Distinctiveness Conflict Risk	Clearly scoped to Laravel backend PHP with distinct, framework-specific triggers; minimal overlap risk with general PHP or other-framework skills.	5 / 5
	Total	20 / 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
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: yaojingang/GEOFlow
Path: .agents/skills/laravel-best-practices/SKILL.md
Commit: 9d70db0

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.