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.
94
92%
Does it follow best practices?
Impact
97%
1.14xAverage score across 3 eval scenarios
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 abundant 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. The description is well-structured and concise without unnecessary padding.
| 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 capabilities listed) and 'when' (explicit 'Use when...' clause listing six distinct trigger scenarios like creating models, setting up queues, implementing auth, etc.). | 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
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, well-structured Laravel skill with excellent actionability through complete code templates and specific artisan commands. The progressive disclosure via the reference table is well-designed, and the validation checkpoints provide clear verification steps. Minor weaknesses include some unnecessary verbosity (self-description, knowledge reference keyword dump) and code templates that could potentially be moved to reference files to keep the main skill leaner.
Suggestions
Remove the opening self-description line ('Senior Laravel specialist...') as it wastes tokens and doesn't instruct behavior.
Move or remove the 'Knowledge Reference' keyword dump at the end — it adds no actionable guidance.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is generally well-structured but includes some unnecessary verbosity. The opening line 'Senior Laravel specialist with deep expertise...' is self-description that wastes tokens. The code templates, while useful, are quite lengthy and could be trimmed. The 'Knowledge Reference' section at the end is a keyword dump that adds little value. However, most content earns its place. | 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 throughout. The constraints section gives concrete do/don't guidance rather than vague principles. | 3 / 3 |
Workflow Clarity | The core workflow is clearly sequenced with 5 numbered steps, each including specific validation commands. The validation checkpoints table provides explicit verification at each stage with expected results. The workflow includes feedback loops (run tests before considering steps complete, verify migrations ran, check route list). | 3 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a clear reference table pointing to 5 topic-specific files (eloquent.md, routing.md, queues.md, livewire.md, testing.md) with 'Load When' context. References are one level deep and clearly signaled. The main file serves as an effective overview with templates and constraints inline where appropriate. | 3 / 3 |
Total | 11 / 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.
3d95bb1
Table of Contents
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.