Name: wp-abilities-verify
Rating: 69.6 (1 reviews)
Author: WordPress

wp-abilities-verify

Verify a WordPress plugin's Abilities API registrations: enumerate abilities, check that callback behavior matches each annotation's claim (the adversarial readonly-but-writes detection), validate permissions and schemas, and validate audit documents produced by wp-abilities-audit.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

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 skill body is a lean, well-structured verification procedure: concrete commands and a copy-paste report template, an explicitly sequenced workflow with validation checkpoints and feedback loops, and clean one-level-deep progressive disclosure into six real reference files.

Dimension	Reasoning	Score
Conciseness	The body is dense with procedure-specific detail (exact rg flags, annotation predicates, lint principles, report template) and assumes Claude's competence without explaining WordPress or basic programming concepts; every section earns its place.	3 / 3
Actionability	Gives concrete, executable guidance — `rg --multiline --pcre2`, `wp_get_abilities()` over wp-cli, the exact `// verify-ignore: <annotation> -- <reason>` suppression syntax, six specific lint principles, and a copy-paste-ready report template — not vague direction.	3 / 3
Workflow Clarity	A clearly numbered 7-step procedure with explicit validation checkpoints (source-only → FAIL, runtime-only → WARN, single FAIL → top-line FAIL), a false-positive suppression feedback loop, plus dedicated Failure modes and Escalation sections covering error recovery.	3 / 3
Progressive Disclosure	The body is an overview that points to six real, clearly-signaled one-level-deep reference files ('Read `references/xxx.md`'), with detail appropriately split out; verified all referenced files exist in references/.	3 / 3
	Total	12 / 12 Passed

Description

67%

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 clearly occupies a distinct niche, but it omits an explicit 'Use when...' trigger and leans on technical jargon rather than natural user phrasing, capping completeness and trigger-term quality at 2.

Suggestions

Append an explicit trigger clause, e.g. 'Use when verifying a WordPress plugin's Abilities API registrations before a PR lands, or validating an audit doc produced by wp-abilities-audit.'

Soften jargon with natural-language variants a user might say ('abilities don't match their annotations', 'readonly ability writes', 'audit document checks').

Keep the third-person voice (already correct) while adding the 'when' guidance.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'enumerate abilities, check that callback behavior matches each annotation's claim ... validate permissions and schemas, and validate audit documents' — matching the anchor for naming several specific concrete actions.	3 / 3
Completeness	It clearly answers 'what' (enumerate, callback-match, validate permissions/schemas, validate audit docs) but lacks any explicit 'when to use' trigger clause, which the guidelines cap at 2.	2 / 3
Trigger Term Quality	Relevant domain keywords exist ('WordPress plugin', 'Abilities API', 'permissions', 'schemas', 'audit') but the phrasing is technical jargon ('callback behavior matches each annotation's claim', 'adversarial readonly-but-writes detection') and missing common natural-language variations a user would actually say.	2 / 3
Distinctiveness Conflict Risk	A very specific niche — verifying WordPress plugin Abilities API registrations — with triggers unlikely to overlap with other skills, matching the 'clear niche with distinct triggers' anchor.	3 / 3
	Total	10 / 12 Passed

Validation

100%

Warnings & errors only

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: WordPress/agent-skills
Path: skills/wp-abilities-verify/SKILL.md
Commit: 120d309

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.