laravel-expert
Build Production Laravel Features
Laravel projects need consistent architecture, validation, security, and performance discipline. This skill guides Claude, Codex, and Claude Code toward idiomatic Laravel solutions.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "laravel-expert" from https://skillstore.io/skills/sickn33-laravel-expert.md and its manifest at https://skillstore.io/api/skills/sickn33-laravel-expert/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "laravel-expert". Design a Laravel API endpoint for creating orders.
Expected outcome:
- Architecture overview with routes, controller action, FormRequest validation, policy checks, service layer, resource response, and job boundaries.
- Notes on transactions, idempotency, eager loading, and expected validation errors.
Using "laravel-expert". Review a controller that validates input inside each action.
Expected outcome:
- Findings that highlight repeated validation, missing authorization, and possible mass assignment risk.
- A refactoring plan that moves validation to FormRequest classes and business logic to a service.
Using "laravel-expert". Improve an endpoint with slow database queries.
Expected outcome:
- Recommendations for eager loading, query scopes, pagination, indexes, and cache invalidation rules.
- A short explanation of how each change affects correctness and performance.
Security Audit
SafeI found no evidence of malicious intent or unsafe behavior in SKILL.md. All nine static findings are false positives caused by benign Laravel guidance such as avoiding legacy patterns, raw queries, and blind request input. No semantic findings were identified.
Risk Factors
🌐 Network access (1)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/sickn33-laravel-expert/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-laravel-expert?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-laravel-expert?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-laravel-expert/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-laravel-expert.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
sickn33. (2026). laravel-expert security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-laravel-expert/audits/4BibTeX citation
@techreport{sickn33-sickn33-laravel-expert-2026,
author = {sickn33},
title = {laravel-expert security audit report (audit version 4)},
institution = {Skillstore},
year = {2026},
number = {4},
url = {https://skillstore.io/skills/sickn33-laravel-expert/audits/4},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "laravel-expert security audit report (audit version 4)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-07"
url: "https://skillstore.io/skills/sickn33-laravel-expert/audits/4"
identifiers:
- type: other
value: "skillstore:sickn33-laravel-expert:audit:4"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Design a Laravel Feature
Plan a new backend feature with routes, controllers, services, validation, authorization, resources, and tests.
Refactor Legacy Laravel Code
Move business logic out of controllers, reduce duplication, and align code with Laravel conventions.
Review API Quality
Evaluate API responses, validation, authorization, pagination, rate limiting, and database access patterns.
Try These Prompts
Review this Laravel controller for validation, authorization, readability, and framework conventions. Explain the top issues first.
Design a Laravel CRUD feature for this domain model. Include routing, validation, policies, resources, and service responsibilities.
Refactor this Laravel service flow to reduce coupling, improve testability, and preserve existing behavior. Explain the tradeoffs.
Audit this Laravel API module for authorization gaps, validation risks, N+1 queries, transaction boundaries, and response consistency.
Best Practices
- Provide the Laravel version, related models, routes, policies, and failing tests when asking for implementation help.
- Ask for security, authorization, validation, and database behavior to be reviewed together.
- Request tradeoffs when choosing between services, jobs, events, observers, and policies.
Avoid
- Do not use this skill for non-Laravel PHP architecture decisions.
- Do not ask for raw queries or mass assignment shortcuts without explaining the safety constraints.
- Do not expect cloud, queue, cache, or package choices without project requirements.