CtrlK
BlogDocsLog inGet started
Tessl Logo

wp-plugin-development

Use when developing WordPress plugins: architecture and hooks, activation/deactivation/uninstall, admin UI and Settings API, data storage, cron/tasks, security (nonces/capabilities/sanitization/escaping), and release packaging.

75

Quality

92%

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

85%

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

A well-structured, token-efficient overview with strong progressive disclosure and validation checkpoints. The main weakness is actionability: the body names APIs and gives guidelines but provides almost no inline executable patterns, pushing all concrete code into the references.

Suggestions

Add one minimal inline executable snippet per major step (e.g., a register_activation_hook + flush_rewrite_rules skeleton in lifecycle, or a register_setting/add_settings_field block in settings-api) so the body is actionable without opening references.

Show expected output/exit behavior of the triage scripts and a decision branch for when detect_plugins.mjs finds zero or multiple plugins.

Inline a short canonical nonce + capability-check security pattern rather than only naming the functions, since security is flagged as 'always'.

DimensionReasoningScore

Conciseness

Lean bullet points with no padding about what WordPress or hooks are; it assumes Claude's competence and every line carries guidance (e.g., 'Validate/sanitize input early; escape output late').

3 / 3

Actionability

Concrete triage commands ('node .../detect_plugins.mjs') and named APIs (register_setting(), $wpdb->prepare(), wp_unslash()) are present, but the body is guideline-level with no inline executable code blocks, deferring executable detail to references.

2 / 3

Workflow Clarity

A numbered 0–5 procedure is clearly sequenced, with an explicit Verification section (activates with no fatals, settings save/read, uninstall removes data, run tests) and a Failure modes/debugging section for error recovery.

3 / 3

Progressive Disclosure

The body is an overview pointing one level deep to clearly signaled references (references/structure.md, lifecycle.md, settings-api.md, security.md, data-and-cron.md, debugging.md), all of which exist as real files.

3 / 3

Total

11

/

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.

A strong, concise description: third-person, with an explicit 'Use when' trigger and a concrete list of capability domains. It clearly communicates both what the skill does and when to invoke it.

DimensionReasoningScore

Specificity

Lists multiple concrete action domains — 'architecture and hooks, activation/deactivation/uninstall, admin UI and Settings API, data storage, cron/tasks, security (nonces/capabilities/sanitization/escaping), and release packaging' — rather than vague language.

3 / 3

Completeness

The explicit 'Use when developing WordPress plugins:' clause states when, and the colon-separated list states what, so both questions are answered with an explicit trigger.

3 / 3

Trigger Term Quality

'Use when developing WordPress plugins' is a natural trigger a user would say, and sub-terms (hooks, Settings API, nonces, capabilities, sanitization) match real WordPress developer vocabulary.

3 / 3

Distinctiveness Conflict Risk

Scoped tightly to WordPress plugin development, a clear niche unlikely to overlap with general PHP skills or the separate wp-project-triage skill.

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.