php-pro
Use when building PHP applications with modern PHP 8.3+ features, Laravel, or Symfony frameworks. Invokes strict typing, PHPStan level 9, async patterns with Swoole, and PSR standards. Creates controllers, configures middleware, generates migrations, writes PHPUnit/Pest tests, defines typed DTOs and value objects, sets up dependency injection, and scaffolds REST/GraphQL APIs. Use when working with Eloquent, Doctrine, Composer, Psalm, ReactPHP, or any PHP API development.
93
92%
Does it follow best practices?
Impact
92%
1.08xAverage score across 6 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 a strong skill description that excels across all dimensions. It provides comprehensive concrete actions, rich trigger terms spanning the PHP ecosystem, explicit 'Use when' guidance, and a clearly distinct niche. The description is well-structured and information-dense without being padded or vague.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: creates controllers, configures middleware, generates migrations, writes PHPUnit/Pest tests, defines typed DTOs and value objects, sets up dependency injection, and scaffolds REST/GraphQL APIs. | 3 / 3 |
Completeness | Clearly answers both 'what' (creates controllers, configures middleware, generates migrations, writes tests, scaffolds APIs, etc.) and 'when' with two explicit 'Use when' clauses covering PHP 8.3+ applications, Laravel/Symfony frameworks, and specific tools like Eloquent, Doctrine, Composer, and PHP API development. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: PHP, Laravel, Symfony, Eloquent, Doctrine, Composer, PHPUnit, Pest, Swoole, ReactPHP, GraphQL, REST API, migrations, middleware, DTOs, PHPStan, Psalm, PSR. These are terms PHP developers naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear PHP ecosystem niche. The specific mention of PHP 8.3+, Laravel, Symfony, Eloquent, Doctrine, PHPStan, Swoole, and other PHP-specific tools makes it very unlikely to conflict with skills for other languages or frameworks. | 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 skill with excellent actionability through complete code examples, clear workflow with validation checkpoints, and well-structured progressive disclosure via the reference table. The main weakness is moderate verbosity — some constraints state things Claude already knows (security basics, no var_dump in production), and the Knowledge Reference section is a non-actionable keyword dump. Trimming these would improve token efficiency.
Suggestions
Remove obvious security constraints Claude already knows (e.g., 'Store passwords in plain text', 'Write SQL queries vulnerable to injection') to reduce token waste.
Remove the 'Knowledge Reference' keyword list at the bottom — it provides no actionable guidance and wastes tokens.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-structured but includes some redundancy. The MUST DO/MUST NOT DO lists contain items Claude already knows (e.g., don't store passwords in plain text, don't write SQL injection-vulnerable queries). The 'Knowledge Reference' section at the bottom is just a keyword list that adds no actionable value. The code examples are useful but collectively make the file quite long when references could handle the detail. | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste-ready PHP code examples for DTOs, services, tests, and enums. Specific commands are given for PHPStan and PHPUnit. The code patterns are complete with namespaces, imports, and proper structure — not pseudocode. | 3 / 3 |
Workflow Clarity | The core workflow is clearly sequenced (analyze → design → implement → secure → verify) with explicit validation checkpoints: run PHPStan level 9, fix all errors before proceeding, run tests, enforce 80%+ coverage, and only deliver when both pass clean. This is a proper feedback loop for verification. | 3 / 3 |
Progressive Disclosure | The reference table with 'Load When' conditions is an excellent progressive disclosure pattern — it clearly signals when to load each reference file and keeps the main skill as an overview. References are one level deep and well-organized by topic. | 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.
- Repository
- jeffallan/claude-skills
- Commit
3d95bb1
- 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.