CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

wordpress-php-dev

WordPress PHP plugin development using Test-Driven Development (TDD) and functional programming principles. Use this skill when developing, testing, or maintaining WordPress plugins with focus on PSR-12 compliance, Composer integration, automated testing with PHPUnit, coding standards enforcement with phpcs/phpcbf, and git version control. Triggers include requests to create WordPress plugins, write WordPress PHP code, set up testing infrastructure, implement TDD workflows, or apply functional programming patterns in WordPress.

Quality

83%

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

73%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 highly actionable with an explicitly validated TDD workflow and well-structured, one-level-deep references to real bundle files. Its weaknesses are redundancy — the TDD cycle and best-practices content are repeated, and some examples teach patterns Claude already knows — and inlining of detail that belongs in the references.

Suggestions

Remove the duplicate workflow presentation: merge 'Initial Development Workflow' into the 'Core Development Workflow' TDD cycle rather than presenting the same five steps twice.

Trim or move inline detail into the reference files — the singleton Plugin example, pipe() composition helper, and phpcs.xml property configuration could live in references/functional_patterns.md or a standards reference, shortening the overview body.

Replace the non-executable 'view references/*.md' commands with direct instructions like 'Read references/tdd_patterns.md' so every command in the body is actionable as written.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete commands and code, but includes unnecessary padding: the TDD cycle appears twice ('Initial Development Workflow' then the fuller 'Core Development Workflow'), the 'Best Practices Summary' restates earlier sections, and the singleton Plugin class and pipe() composition helper explain patterns Claude already knows. Mostly efficient with some clear tightening opportunities fits the middle anchor better than the noticeably-verbose anchor.

3 / 5

Actionability

Mostly executable guidance — exact composer commands, step-by-step bash TDD sequence, complete PHP snippets, and concrete phpcs.xml config XML. Minor gap: 'view references/tdd_patterns.md' is not an executable command and should be 'Read', keeping it just below the fully copy-paste-ready anchor.

4 / 5

Workflow Clarity

The TDD cycle is explicitly sequenced with validation checkpoints ('composer test # Should fail (RED)', '# Should pass (GREEN)') after each phase, commit steps interleaved, and a Troubleshooting section providing error-recovery feedback loops — matching the top anchor.

5 / 5

Progressive Disclosure

Good structure with three real, verified one-level-deep reference files, each clearly signaled with its key topics listed, plus asset templates and an init script. Minor organization gap: the ~460-line body inlines substantial content (Common Patterns, singleton example, phpcs config detail) that would fit better in the reference files, keeping it below the clean-overview anchor.

4 / 5

Total

16

/

20

Passed

Description

83%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 strong description: it names a clear niche, enumerates specific tooling capabilities, and provides an explicit 'Use this skill when...' clause with concrete trigger phrases. Minor improvements possible in trigger synonyms and sharpening the generic TDD/FP triggers to the WordPress context.

DimensionReasoningScore

Specificity

Lists several specific capabilities with named tooling — 'PSR-12 compliance, Composer integration, automated testing with PHPUnit, coding standards enforcement with phpcs/phpcbf, and git version control' — with minor coverage gaps. Not 5 because actions are framed as focus areas rather than a comprehensive set of concrete operations; not 3 because it goes well beyond naming 1-2 actions.

4 / 5

Completeness

Explicitly answers both what ('WordPress PHP plugin development using Test-Driven Development (TDD) and functional programming principles' with enumerated focus areas) and when ('Use this skill when developing, testing, or maintaining WordPress plugins... Triggers include requests to...'), with concrete trigger phrases matching the top anchor.

5 / 5

Trigger Term Quality

Good natural keyword coverage: 'create WordPress plugins, write WordPress PHP code, set up testing infrastructure, implement TDD workflows', with TDD both spelled out and abbreviated. Missing a few natural synonyms and phrasing variations (e.g. '.php' extensions, 'plugin development'), so it falls short of the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

Clear niche in WordPress PHP plugin development, distinguishable from related skills. Minor overlap risk remains because triggers like 'implement TDD workflows' and 'apply functional programming patterns' could also match generic TDD or functional-programming skills.

4 / 5

Total

17

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

stephenfeather/claude-skills

Path

wordpress-php-dev/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.