CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

php-development

Architect, build, test, refactor, and maintain modern PHP 8.0-8.4 applications, libraries, and APIs using strict typing, modern language features, PSR standards, Composer dependency management, PDO database access, PHPUnit/Pest testing, PHPStan/Psalm static analysis, and secure coding practices.

61

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/development-skills/php-development/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-sequenced guide with real bundle structure and explicit verification commands, weakened mainly by verbosity: substantial PHP language-feature demonstrations duplicate what the reference file already provides and what Claude already knows.

Suggestions

Move the PHP 8.x language-feature demonstrations (union/intersection/DNF types, enums, match, attributes, fibers) into references/modern-php-patterns.md, keeping only the prescriptive rules (e.g. "declare(strict_types=1) in every file") in the body.

Tighten steps 2-5 to the standard being enforced plus a one-line pointer, cutting roughly 300 lines of examples Claude already knows.

Add a short per-step validation cue (e.g. run "composer validate" right after step 1, "vendor/bin/phpstan analyse" after the typing steps) so feedback loops are interleaved rather than only in the final Verification section.

DimensionReasoningScore

Conciseness

Sections 2-5 re-demonstrate PHP 8 language features (enums, match expressions, attributes, named arguments) that Claude already knows and that duplicate the reference file's feature cheatsheet, so the body could be tightened. It is not 2 because most sections (Composer config, phpstan.neon, OPcache, verification) are dense and earn their tokens, and not 4 because roughly 300 lines of feature demos are unnecessary in the main file.

3 / 5

Actionability

The body is fully executable throughout: complete composer.json, phpstan.neon, .php-cs-fixer config, php.ini snippets, runnable PHP classes, and shell commands ("composer dump-autoload -o -a", "find src tests -name \"*.php\" -exec php -l"), covering the common cases copy-paste ready. It is not 4 because no execution gaps were found.

5 / 5

Workflow Clarity

Twelve clearly sequenced steps plus a dedicated Verification section with six concrete validation commands (lint, composer audit, phpstan, phpunit/pest, php-cs-fixer dry-run) provide explicit checkpoints, and the PDO section shows a rollback feedback loop. It is not 5 because validation is consolidated at the end rather than interleaved as per-step feedback loops, and not 3 because checkpoints are explicit and complete.

4 / 5

Progressive Disclosure

The body signals a single one-level-deep reference ("For detailed pattern implementations, code cheatsheets, and production templates, refer to references/modern-php-patterns.md") which exists and contains no nested references. It is not 5 because the main file inlines language-feature demonstrations that duplicate the reference's cheatsheet instead of cleanly splitting content.

4 / 5

Total

16

/

20

Passed

Description

71%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A dense, specific, third-person description that clearly states what the skill does with a comprehensive toolchain, but it omits any explicit "Use when..." trigger guidance, capping completeness. Adding trigger phrases would make it fully strong.

Suggestions

Append a trigger clause such as "Use when writing, refactoring, or upgrading PHP code, configuring Composer, or adding tests/static analysis to a PHP project" to satisfy the completeness dimension.

Add natural trigger variations users actually say, e.g. ".php files", "legacy PHP 5/7 upgrade", or "PHP 8 migration", to broaden trigger-term coverage.

Clarify the boundary with adjacent skills by stating whether framework-specific work (Laravel/Symfony) is in or out of scope.

DimensionReasoningScore

Specificity

"Architect, build, test, refactor, and maintain modern PHP 8.0-8.4 applications, libraries, and APIs" lists five concrete actions plus a specific toolchain (PDO, PHPUnit/Pest, PHPStan/Psalm, Composer, PSR standards), matching the comprehensive-coverage anchor. It is not 4 because there are no meaningful gaps in the action coverage.

5 / 5

Completeness

The "what" is clear and concrete, but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guidelines. It is not 4 because the "when" is only weakly implied by the domain mention, never stated.

3 / 5

Trigger Term Quality

Natural terms users would say are present ("PHP", "Composer", "PHPUnit", "Pest", "PHPStan", "Psalm", "PDO", "refactor"), giving good keyword coverage. It is not 5 because common variations like ".php files", "legacy PHP upgrade", or framework names (Laravel/Symfony) are missing.

4 / 5

Distinctiveness Conflict Risk

PHP 8.0-8.4 with named tools (PDO, Pest, PHPStan) carves a clear niche with mostly distinct triggers. It is not 5 because the boundary with framework-specific skills (Laravel, Symfony) is unstated, leaving minor overlap risk.

4 / 5

Total

16

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (842 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

administrakt0r/pro-skills-repo-administraktor

Path

skills/development-skills/php-development/SKILL.md

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.