laravel-specialist
Build and configure Laravel 10+ applications, including creating Eloquent models and relationships, implementing Sanctum authentication, configuring Horizon queues, designing RESTful APIs with API resources, and building reactive interfaces with Livewire. Use when creating Laravel models, setting up queue workers, implementing Sanctum auth flows, building Livewire components, optimising Eloquent queries, or writing Pest/PHPUnit tests for Laravel features.
72
88%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
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 excellent skill description that covers all evaluation dimensions strongly. It provides specific concrete actions, includes a comprehensive set of natural trigger terms that Laravel developers would use, explicitly states both what the skill does and when to use it, and is highly distinctive through its Laravel-ecosystem-specific terminology.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: creating Eloquent models and relationships, implementing Sanctum authentication, configuring Horizon queues, designing RESTful APIs with API resources, and building reactive interfaces with Livewire. | 3 / 3 |
Completeness | Clearly answers both 'what' (build and configure Laravel applications with specific subsystems) and 'when' with an explicit 'Use when...' clause listing six distinct trigger scenarios. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms a user would say: 'Laravel', 'Eloquent', 'Sanctum', 'Horizon', 'Livewire', 'queue workers', 'API resources', 'Pest', 'PHPUnit', 'models', 'auth flows'. These are all terms Laravel developers naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with Laravel-specific terminology (Eloquent, Sanctum, Horizon, Livewire, Pest) that clearly distinguishes it from generic PHP, web framework, or other language skills. Very unlikely to conflict with non-Laravel skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, well-structured Laravel skill with excellent actionability through complete code templates and clear workflow with validation checkpoints. Its main weaknesses are moderate verbosity—the constraints section restates many best practices Claude already knows, and the extensive inline code templates could be moved to the referenced (but non-existent) bundle files. The progressive disclosure design is good in concept but undermined by missing bundle files and too much inline content.
Suggestions
Trim the MUST DO / MUST NOT DO constraints to only non-obvious, Laravel-specific guidance—remove items like 'follow PSR-12' or 'don't skip validation' that Claude already knows.
Move the code templates into the referenced files (e.g., references/eloquent.md) and keep only a single brief example inline, since the templates make the SKILL.md very long.
Provide the actual bundle reference files (references/eloquent.md, references/routing.md, etc.) so the progressive disclosure structure functions as designed.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary framing ('Senior Laravel specialist with deep expertise...') and the constraints section lists many items Claude already knows (PSR-12, don't use raw queries, don't skip validation). The code templates are useful but collectively make the file quite long; some could be offloaded to reference files. | 2 / 3 |
Actionability | Excellent actionability with fully executable, copy-paste-ready code templates for models, migrations, API resources, queued jobs, and Pest tests. Specific artisan commands are provided at each stage, and the code uses modern PHP 8.2+ patterns with proper type hints and declarations. | 3 / 3 |
Workflow Clarity | The core workflow is clearly sequenced with numbered steps, each including specific verification commands. The validation checkpoints table provides explicit commands and expected results at each stage, creating clear feedback loops (e.g., migrate then check status, test then verify coverage). | 3 / 3 |
Progressive Disclosure | The reference table with 'Load When' guidance is well-structured and signals one-level-deep references clearly. However, no bundle files are provided, so the referenced files (references/eloquent.md, references/routing.md, etc.) don't actually exist, and the inline code templates are extensive content that could have been offloaded to those reference files to keep the SKILL.md leaner. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- jeffallan/claude-skills
- Commit
e8be415
- Reviewed
Table of Contents
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.