CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

php-pro

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

49

Quality

62%

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

40%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 skill body is well-structured and token-efficient but provides almost no executable guidance — it lists topics and principles rather than code or a concrete workflow. Actionability and workflow clarity are the main weaknesses.

Suggestions

Add copy-paste-ready PHP code examples for the core capabilities (generators, SPL structures, match/enum, strict typing) so guidance is executable.

Replace the principle list in 'Approach' with a concrete, sequenced procedure (e.g., profile -> identify bottleneck -> apply SPL/generator -> benchmark) with a validation/benchmark checkpoint.

Trim generic filler in 'Instructions' and 'Output' (e.g., 'Provide actionable steps and verification', 'Clean architecture following SOLID principles') that adds no PHP-specific signal.

DimensionReasoningScore

Conciseness

The body is lean and does not over-explain PHP concepts, but the generic 'Instructions' and nine-item 'Output' sections contain filler ('Provide actionable steps and verification', 'Clean architecture following SOLID principles') that could be trimmed.

3 / 5

Actionability

Guidance is high-level and abstract ('Use generators for large datasets', 'Apply strict typing') with no executable code, commands, or pseudocode, so it offers minimal concrete instruction.

2 / 5

Workflow Clarity

The numbered 'Approach' list reads as best-practice principles rather than a sequenced procedure, and validation/feedback checkpoints are entirely absent.

2 / 5

Progressive Disclosure

Content is organized into clearly headed sections with no nested references, appropriate for a compact skill; minor gaps come from generic template sections ('Use this skill when', 'Do not use this skill when').

4 / 5

Total

11

/

20

Passed

Description

67%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 is specific and answers both what and when with appropriate third-person voice, but its trigger phrase is narrow and lacks keyword variations or file extensions. It is solid but not maximally triggerable.

Suggestions

Broaden the 'Use when' clause with concrete natural triggers such as 'PHP files, .php scripts, performance-critical PHP, or refactoring legacy PHP'.

Add file-extension and synonym keywords (e.g., '.php', 'PHP 8+', 'SPL') to improve trigger term coverage.

Reframe feature topics as concrete actions (e.g., 'Build memory-efficient pipelines with generators') to lift specificity toward a 5.

DimensionReasoningScore

Specificity

Names the PHP domain and several concrete capabilities ('generators, iterators, SPL data structures, and modern OOP features'), but describes feature topics rather than discrete actions, leaving minor coverage gaps.

4 / 5

Completeness

Explicitly states what it does ('Write idiomatic PHP code with...') and when to use it ('Use PROACTIVELY for high-performance PHP applications'), though the trigger condition is narrow rather than a set of concrete phrases.

4 / 5

Trigger Term Quality

Repeats 'PHP' and 'high-performance PHP applications' as triggers but omits common variations, synonyms, or file extensions (.php), so keyword coverage is only moderate.

3 / 5

Distinctiveness Conflict Risk

The PHP niche with specific feature mentions is mostly distinct with only minor overlap risk against broader PHP skills, falling just short of a fully clear niche.

4 / 5

Total

15

/

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.