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.
92
96%
Does it follow best practices?
Impact
83%
1.23xAverage score across 3 eval scenarios
High
Do not use without reviewing
Security
1 high severity finding. You should review these findings carefully before considering using this skill.
W008: Secret detected in skill content (API keys, tokens, passwords).
What this means
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.
Why it was flagged
I flagged two literal credential-like values found in the docs. Although they appear inside an ".env committed / incorrect" example, they are realistic-looking API secrets rather than obvious placeholders (e.g., "YOUR_API_KEY" or "sk-xxxx"). Specifically: - "STRIPE_SECRET=sk_live_abc123" matches the common Stripe secret key naming pattern (sk_live_...), and even though it contains "abc123", the prefix makes it look like a real secret credential included in the file. - "AWS_SECRET_ACCESS_KEY=wJalrXUtnFEMI" is a literal secret-like value (random-looking characters) used as an AWS secret example. Per the rule to only flag literal, usable credentials present in documentation, these two entries are direct secret assignments and should be treated as leaks (or at least removed/replaced with placeholders).
- Repository
- laravel/boost
- Commit
21009e9
- Audited
- Security analysis
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.