php-pro
Use when building PHP applications with modern PHP 8.3+ features, Laravel, or Symfony frameworks. Invoke for strict typing, PHPStan level 9, async patterns with Swoole, PSR standards.
Overall
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.
The description excels at trigger terms and distinctiveness with excellent PHP ecosystem keyword coverage, making it easy to identify when PHP development is needed. However, it lacks specificity about what concrete actions the skill performs - it reads more like a list of technologies than a description of capabilities. The 'what' portion needs concrete verbs describing actions like 'generates', 'refactors', 'implements'.
Suggestions
Add concrete action verbs describing what the skill does, e.g., 'Generates PHP 8.3+ code with strict typing, builds Laravel/Symfony applications, implements async patterns with Swoole'
Restructure to lead with capabilities before the 'Use when' clause to clearly separate what it does from when to use it
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names domain (PHP applications) and mentions specific technologies (Laravel, Symfony, Swoole, PHPStan) but doesn't list concrete actions - it describes what to use rather than what actions the skill performs. | 2 / 3 |
Completeness | Has a 'Use when' clause which is good, but the 'what' is weak - it describes contexts and technologies rather than concrete capabilities. The description tells when to invoke but not what specific actions the skill performs. | 2 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'PHP', 'PHP 8.3', 'Laravel', 'Symfony', 'strict typing', 'PHPStan', 'async', 'Swoole', 'PSR standards' - these are all terms developers naturally use when discussing PHP development. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche targeting modern PHP development with specific framework mentions (Laravel, Symfony), tooling (PHPStan level 9, Swoole), and version requirements (PHP 8.3+) - unlikely to conflict with other language or general coding skills. | 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 with clear progressive disclosure through reference files, but critically lacks executable code examples for a programming-focused skill. The content is moderately verbose with persona framing that doesn't add value, and the workflow lacks explicit validation checkpoints despite mentioning PHPStan compliance as a requirement.
Suggestions
Add concrete, executable PHP code examples showing strict typing, readonly properties, and at least one Laravel/Symfony pattern - the skill describes patterns but never demonstrates them
Remove the role definition paragraph and '10+ years of experience' persona framing - Claude doesn't need this context to execute the skill
Integrate validation steps into the workflow with explicit feedback loops, e.g., '4. Run PHPStan: `vendor/bin/phpstan analyse --level=9` - fix all errors before proceeding'
Fix the inconsistency in MUST NOT DO section that mentions 'Pydantic V1 patterns' which is Python, not PHP
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Contains some unnecessary padding like the role definition paragraph and 'Senior PHP developer with 10+ years of experience' persona framing that Claude doesn't need. The constraints section is efficient, but the overall structure could be tighter. | 2 / 3 |
Actionability | No executable code examples provided despite being a programming skill. The guidance is abstract ('Create typed domain models', 'Write strict-typed code') without concrete PHP code snippets showing actual implementation patterns. | 1 / 3 |
Workflow Clarity | The 5-step core workflow provides a sequence but lacks validation checkpoints and feedback loops. Steps like 'Run PHPStan level 9 before delivery' are mentioned in constraints but not integrated into the workflow with explicit verification steps. | 2 / 3 |
Progressive Disclosure | Well-structured with clear reference table pointing to specific topic files with explicit 'Load When' conditions. References are one level deep and clearly signaled with a navigation table. | 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.