laravel-specialist
Use when building Laravel 10+ applications requiring Eloquent ORM, API resources, or queue systems. Invoke for Laravel models, Livewire components, Sanctum authentication, Horizon queues.
Install with Tessl CLI
npx tessl i github:jeffallan/claude-skills --skill laravel-specialistOverall
score
61%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
72%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 description excels at trigger term coverage and distinctiveness with Laravel-specific terminology, making it easy to identify when Laravel development is needed. However, it lacks concrete action verbs describing what the skill actually does - it reads more like a technology checklist than a capability description. The 'what' component needs strengthening with specific actions like 'create models', 'configure authentication', or 'set up queue workers'.
Suggestions
Add concrete action verbs describing capabilities, e.g., 'Creates Eloquent models and relationships, implements API resources, configures queue workers and Horizon dashboards'
Restructure to lead with what the skill does before listing when to use it, following the pattern: '[Actions]. Use when [triggers].'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Laravel 10+) and mentions specific components (Eloquent ORM, API resources, queue systems, Livewire, Sanctum, Horizon), but doesn't describe concrete actions - only lists technologies without explaining what actions can be performed with them. | 2 / 3 |
Completeness | Has explicit 'Use when' and 'Invoke for' clauses addressing when to use it, but the 'what does this do' is weak - it only lists technologies without describing capabilities or actions (e.g., 'building' is vague, no mention of what operations are supported). | 2 / 3 |
Trigger Term Quality | Excellent coverage of natural terms Laravel developers would use: 'Laravel', 'Eloquent ORM', 'API resources', 'queue systems', 'models', 'Livewire components', 'Sanctum authentication', 'Horizon queues' - these are all terms users would naturally mention. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with Laravel-specific terminology (Eloquent, Livewire, Sanctum, Horizon) that clearly separates it from generic PHP or web development skills. The version specification (10+) adds further precision. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill has good structural organization and progressive disclosure with clear references to detailed topic files. However, it severely lacks actionability - there are no code examples, no executable commands, and no concrete templates despite claiming to provide 'Output Templates'. The content reads more like a job description than actionable guidance for Claude.
Suggestions
Add concrete, executable code examples for common patterns (e.g., a complete Eloquent model with relationships, an API resource transformation, a queued job)
Replace the abstract 'Output Templates' section with actual code templates showing the expected structure of model files, migrations, and tests
Add validation checkpoints to the Core Workflow (e.g., 'Run php artisan test after step 4', 'Verify migrations with php artisan migrate:status')
Remove the role-playing preamble ('You are a senior PHP engineer...') as it wastes tokens without adding actionable value
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Contains some unnecessary role-playing setup ('You are a senior PHP engineer with 10+ years...') and verbose sections like 'When to Use This Skill' that Claude doesn't need. The constraints and knowledge reference sections are reasonably efficient. | 2 / 3 |
Actionability | No executable code examples anywhere. The skill describes what to do abstractly ('Create Eloquent models with relationships') but provides zero concrete code, commands, or copy-paste ready snippets. Output templates list file types but no actual templates. | 1 / 3 |
Workflow Clarity | The 5-step core workflow provides a sequence but lacks validation checkpoints. No feedback loops for error recovery, no specific commands to run, and no verification steps between stages. The reference table is helpful for navigation but doesn't constitute workflow guidance. | 2 / 3 |
Progressive Disclosure | Well-structured with clear sections and a reference table pointing to topic-specific files (eloquent.md, routing.md, etc.) with clear 'Load When' guidance. One level deep, clearly signaled references. | 3 / 3 |
Total | 8 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_examples | No examples detected (no code fences and no 'Example' wording) | Warning |
Total | 12 / 16 Passed | |
- 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.