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.
72
89%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
High
Do not use without reviewing
Security
1 high severity finding. You should review these findings carefully before considering using this skill.
Detected sensitive credentials directly embedded within the skill content, such as API keys, access tokens, private keys, or service-specific secrets. Secrets should never be hardcoded in plain text within skill instructions.
I scanned the skill files for literal, credential-like values. I flagged two lines in rules/config.md because they contain explicit API-secret-style assignments (STRIPE_SECRET=sk_live_abc123 and AWS_SECRET_ACCESS_KEY=wJalrXUtnFEMI). These are not generic placeholders (e.g., YOUR_API_KEY) nor obvious low-security setup passwords; they follow real API key environment-variable patterns and therefore qualify as secrets in this scan. I did not flag other strings (emails, config keys, or code examples that reference config() only) because they are not high-entropy credentials or are merely variable names/placeholders.
9d70db0
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.