CtrlK
BlogDocsLog inGet started
Tessl Logo

wp-phpstan

Use when configuring, running, or fixing PHPStan static analysis in WordPress projects (plugins/themes/sites): phpstan.neon setup, baselines, WordPress-specific typing, and handling third-party plugin classes.

80

Quality

100%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

The body is a well-organized instruction skill: a deterministic inspect script, a sequenced procedure, explicit verification checkpoints, and one-level-deep references that all resolve to real bundle files. It is concise and actionable without padding.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it never explains what PHPStan or WordPress are — and each line (procedure steps, package names, type patterns) earns its place, matching the 'lean and efficient' anchor.

3 / 3

Actionability

Provides executable commands (`node skills/wp-phpstan/scripts/phpstan_inspect.mjs`, `composer run phpstan`, `vendor/bin/phpstan analyse`) and concrete type patterns (`WP_REST_Request<…>`, `@param`); for an instruction-only skill the guidance is actionable rather than abstract, so the absence of full code blocks is not penalized per the scoring notes.

3 / 3

Workflow Clarity

A clearly sequenced numbered procedure (0–5) is paired with an explicit Verification section (re-run after ignoreErrors changes) and Failure-modes/feedback loops, satisfying the 'clear sequence with explicit validation steps and feedback loops' anchor.

3 / 3

Progressive Disclosure

Overview lives in SKILL.md with one-level-deep, clearly signaled 'See:' references to configuration.md, wordpress-annotations.md, and third-party-classes.md — all real files in ./references — plus a real script in ./scripts, matching the well-structured top anchor.

3 / 3

Total

12

/

12

Passed

Description

100%

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, trigger-rich, and well-scoped: it states concrete capabilities and gives an explicit 'Use when' clause tied to PHPStan-in-WordPress work. It is clearly distinguishable from generic analysis skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'configuring, running, or fixing PHPStan static analysis', 'phpstan.neon setup, baselines, WordPress-specific typing, and handling third-party plugin classes' — matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Clearly answers both what (the listed actions) and when via the explicit 'Use when configuring, running, or fixing PHPStan…' trigger clause, matching the top anchor; voice is the imperative trigger form, not first/second person, so no penalty applies.

3 / 3

Trigger Term Quality

Natural terms a user would actually say are well covered: 'PHPStan', 'WordPress', 'phpstan.neon', 'baselines', 'third-party plugin classes'; not below 2 because common variations are present, and not above since the scale caps at 3.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche (PHPStan static analysis within WordPress projects) with distinct triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
WordPress/agent-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.