CtrlK
BlogDocsLog inGet started
Tessl Logo

php-pro

Write idiomatic PHP code with generators, iterators, SPL data structures, and modern OOP features. Use PROACTIVELY for high-performance PHP applications.

36

Quality

33%

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 ./plugins/AI-Agents-Safe-Coding-Skills/skills/php-pro/SKILL.md

The canonical home for this skill is php-pro in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

17%Scale 1-5

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

This skill is essentially a collection of abstract principles and bullet-point lists about PHP development with no concrete, executable guidance. It reads more like a job description or capability statement than an actionable skill. The complete absence of code examples is a critical gap for a skill about writing idiomatic PHP code, and the referenced implementation playbook doesn't exist in the bundle.

Suggestions

Add concrete, executable PHP code examples for each focus area (e.g., a generator example for memory-efficient processing, an SPL data structure usage example, a PHP 8+ enum/match expression example)

Replace the generic boilerplate sections ('Use this skill when', 'Do not use this skill when', generic instructions) with PHP-specific actionable guidance

Either create the referenced 'resources/implementation-playbook.md' bundle file with detailed examples, or inline the most critical patterns directly in the skill

Add a concrete workflow with validation steps, e.g., 'Profile with Xdebug -> identify bottleneck -> apply generator pattern -> re-profile to verify improvement'

DimensionReasoningScore

Conciseness

The content is padded with generic boilerplate ('Clarify goals, constraints, and required inputs', 'Apply relevant best practices and validate outcomes') that adds no PHP-specific value. The 'Use this skill when' and 'Do not use this skill when' sections are tautological. The Focus Areas and Output sections are lengthy lists of abstract qualities Claude already knows about.

2 / 5

Actionability

There is no executable code, no concrete commands, no specific examples, and no copy-paste ready snippets. The entire skill is abstract guidance ('Use generators for large datasets', 'Apply strict typing') without showing how to do any of it. The reference to 'resources/implementation-playbook.md' is the only concrete pointer, but no bundle file exists to support it.

1 / 5

Workflow Clarity

The 'Approach' section provides a rough numbered sequence but the steps are high-level principles rather than actionable workflow steps. There are no validation checkpoints, no feedback loops, and no concrete verification steps despite the skill claiming to cover performance profiling and optimization.

2 / 5

Progressive Disclosure

The skill references 'resources/implementation-playbook.md' but no bundle files exist to support this reference, making it a broken link. The content that should be in supporting files (detailed examples, code patterns) is neither inline nor properly referenced. The structure is flat lists without meaningful organization for discovery.

2 / 5

Total

7

/

20

Passed

Description

50%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.

The description identifies a clear domain (PHP) and names several specific language features, but falls short on actionable specificity and trigger term coverage. The 'when' guidance is weak—'Use PROACTIVELY for high-performance PHP applications' doesn't give Claude concrete scenarios for skill selection. The description would benefit from explicit trigger phrases and more concrete action verbs describing what the skill actually does.

Suggestions

Add an explicit 'Use when...' clause with concrete trigger scenarios, e.g., 'Use when the user asks about PHP generators, yield statements, SPL data structures, iterator patterns, or optimizing PHP memory usage.'

Replace vague 'Use PROACTIVELY for high-performance PHP applications' with specific use cases like 'processing large datasets with generators, implementing custom iterators, or using SplHeap/SplQueue/SplStack for efficient data handling.'

Include natural synonyms and related terms users might say, such as 'yield', 'lazy evaluation', 'SplFixedArray', 'memory optimization', '.php files', or 'PHP 8 features'.

DimensionReasoningScore

Specificity

Names the domain (PHP) and lists several specific features (generators, iterators, SPL data structures, modern OOP features), but doesn't describe concrete actions beyond 'write code'. It names concepts rather than actionable capabilities like 'implement lazy evaluation with generators' or 'optimize memory usage with SPL structures'.

3 / 5

Completeness

The 'what' is reasonably clear (write idiomatic PHP code with specific features), but the 'when' clause ('Use PROACTIVELY for high-performance PHP applications') is vague and doesn't provide concrete trigger phrases. 'PROACTIVELY' is unusual guidance that doesn't help Claude decide when to select this skill. No explicit 'Use when...' clause with user-facing trigger scenarios.

3 / 5

Trigger Term Quality

Includes relevant PHP-specific terms like 'generators', 'iterators', 'SPL data structures', and 'OOP', but misses common natural user phrases like 'PHP performance', 'memory optimization', 'lazy loading', 'SplHeap', 'SplQueue', 'yield', or file extensions like '.php'.

3 / 5

Distinctiveness Conflict Risk

The mention of specific PHP features (generators, iterators, SPL) provides some distinctiveness, but 'modern OOP features' and 'idiomatic PHP code' are broad enough to overlap with any general PHP coding skill. The 'high-performance' qualifier helps somewhat but is still vague.

3 / 5

Total

12

/

20

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.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.