CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

php-pro

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

Quality

72%

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/php-pro/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is well-organized and appropriately short, with a useful focus-area inventory and an ordered approach, but the guidance stays at the principle level: no code examples, no commands, no named tools, and several sections are boilerplate that restates the description. It functions as a prioritization aid but would be materially stronger with one executable example and concrete validation checkpoints.

Suggestions

Add one compact, executable code example showing the core patterns (e.g., a generator streaming a large dataset and an SplQueue/SplStack usage) so the guidance is copy-paste ready.

Replace 'Profile performance bottlenecks before optimizing' with named tools and commands (e.g., Xdebug cachegrind, Blackfire, phpbench) and add an explicit validate-fix-retry checkpoint after code changes.

Cut the boilerplate 'Use this skill when', 'Do not use this skill when', and generic 'Instructions' sections — they duplicate the frontmatter description and add tokens without new guidance.

DimensionReasoningScore

Conciseness

Lists like 'Focus Areas' and 'Output' are tight and name specifics without over-explaining, but the 'Use this skill when' / 'Do not use this skill when' sections ('Working on php pro tasks or workflows') and generic Instructions bullets ('Clarify goals, constraints, and required inputs', 'Apply relevant best practices and validate outcomes') are boilerplate padding that adds tokens without guidance.

3 / 5

Actionability

Concrete direction exists — named features ('match expressions, enums, attributes, constructor property promotion', 'SplQueue, SplStack, SplHeap') and ordered practices ('Use generators for large datasets to minimize memory footprint') — but there is no code example, command, or tool name anywhere; 'Profile performance bottlenecks before optimizing' names no profiler. Not 2 because the named specifics go beyond high-level hints; not 4 because nothing is executable or copy-paste ready for a code-writing skill.

3 / 5

Workflow Clarity

The 8-step 'Approach' provides a clear sequence with a validation nod ('Test edge cases and error conditions thoroughly', 'Profile performance bottlenecks before optimizing'), but checkpoints are implicit and there is no validate-fix-retry feedback loop. Not 2 because steps are well-defined and ordered; not 4 because validation is generic and not tied to explicit checkpoints.

3 / 5

Progressive Disclosure

The body is roughly 40 content lines with no bundle files present, and it uses well-organized sections (Focus Areas, Approach, Output) with no nested or buried references — matching the simple-skill exception where a short, single-file skill with clean organization scores 5.

5 / 5

Total

14

/

20

Passed

Description

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

The description clearly states what the skill does (idiomatic, modern PHP with generators, iterators, SPL, and OOP) and includes an explicit 'Use for...' trigger scoped to high-performance PHP applications, in proper third-person voice. Keywords are natural for developers, though trigger coverage lacks synonyms, file extensions, and richer 'when the user mentions...' phrases.

DimensionReasoningScore

Specificity

'Write idiomatic PHP code with generators, iterators, SPL data structures, and modern OOP features' lists several concrete capabilities, matching the 'several specific actions; minor gaps' anchor. Not 5 because 'modern OOP features' is broad and the action list is not comprehensive.

4 / 5

Completeness

Has a clear what ('Write idiomatic PHP code with generators, iterators, SPL data structures, and modern OOP features') and an explicit when ('Use for high-performance PHP applications'), matching the both-present-but-when-could-be-more-specific anchor. Not 5 because the when lacks concrete trigger phrases and is narrower than the what.

4 / 5

Trigger Term Quality

Good natural keyword coverage — 'PHP', 'generators', 'iterators', 'SPL data structures', 'high-performance PHP applications' are phrases developers would say. Not 5 because common variations and extensions are missing ('.php', 'PHP 8', 'optimize/debug PHP'); not 3 because coverage goes well beyond one generic keyword.

4 / 5

Distinctiveness Conflict Risk

'generators, iterators, SPL data structures' plus the high-performance framing carves a distinct advanced-PHP niche with minimal conflict risk against non-PHP skills. Not 5 because it could overlap with a hypothetical general PHP skill; not 3 because the technical markers are distinctive.

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

rmyndharis/antigravity-skills

Path

skills/php-pro/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.