tdg-personal/laravel-patterns
Laravel architecture patterns, routing/controllers, Eloquent ORM, service layers, queues, events, caching, and API resources for production apps.
68
68%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
57%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description excels at listing specific Laravel capabilities with strong, natural trigger terms that developers would use. However, it critically lacks a 'Use when...' clause, which means Claude has no explicit guidance on when to select this skill over others. The description reads as a feature list rather than actionable selection criteria.
Suggestions
Add a 'Use when...' clause such as 'Use when the user asks about Laravel framework development, Eloquent models, Laravel routing, middleware, queues, or building PHP applications with Laravel.'
Specify the scope boundary to reduce overlap, e.g., 'Use for Laravel-specific patterns and features, not general PHP or other framework questions.'
Add common user phrasings like 'artisan commands', 'migrations', 'middleware', or 'Laravel project' to improve trigger coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete capabilities: architecture patterns, routing/controllers, Eloquent ORM, service layers, queues, events, caching, and API resources. These are distinct, recognizable Laravel concepts. | 3 / 3 |
Completeness | Describes 'what' well but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, a missing 'Use when...' clause caps completeness at 2, and the 'when' is not even implied beyond 'for production apps', making this a weak 1-2. Scoring 1 as the 'when' is essentially absent. | 1 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Laravel', 'routing', 'controllers', 'Eloquent ORM', 'queues', 'events', 'caching', 'API resources', 'service layers'. These are terms Laravel developers naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | The mention of 'Laravel' specifically creates a clear niche, but without explicit trigger guidance, it could overlap with general PHP skills or web framework skills. The Laravel-specific terms like 'Eloquent ORM' help but the broad scope (architecture, routing, caching, queues) could conflict with general backend development skills. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
64%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, actionable Laravel skill with excellent concrete code examples covering the major architectural patterns. Its main weaknesses are length (could benefit from splitting into referenced sub-files) and some sections (Caching, Configuration, Events/Jobs) that are too vague to be useful — they're either bullet-point truisms or should be fleshed out with code. The workflow dimension suffers from lacking explicit validation/verification steps for multi-step operations.
Suggestions
Split detailed sections (Eloquent patterns, routing, migrations) into separate referenced files to improve progressive disclosure and reduce the main file's token footprint.
Either add concrete code examples for the Caching, Events/Jobs, and Configuration sections or remove them — the current bullet points state things Claude already knows without adding actionable value.
Add validation checkpoints for multi-step workflows, e.g., after migrations run `php artisan migrate:status` to verify, or after cache changes verify with `php artisan cache:clear`.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good code examples, but includes some unnecessary explanatory text (e.g., 'Keep controllers thin. Put orchestration in services and single-purpose logic in actions.') and sections like Caching and Configuration that are bullet-point platitudes without actionable detail, wasting tokens on things Claude already knows. | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste-ready PHP code examples throughout — controllers, actions, models, migrations, form requests, routing, service providers, and API responses. Each pattern is demonstrated with concrete, complete code rather than pseudocode or vague descriptions. | 3 / 3 |
Workflow Clarity | The layered architecture flow (Controllers -> Services -> Actions) is clearly demonstrated with code, and the project structure is well-laid-out. However, there are no explicit validation checkpoints or feedback loops for multi-step processes like migrations, deployment, or cache invalidation — the skill describes patterns but doesn't sequence them with verification steps. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear section headers and a logical progression from structure to routing to models to APIs. However, at ~300 lines it's quite long for a single SKILL.md with no references to supplementary files — the Eloquent patterns, routing details, and migration sections could be split into separate referenced documents. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
Reviewed
Table of Contents