Name: wp-abilities-audit
Rating: 62.4 (1 reviews)
Author: WordPress

wp-abilities-audit

Audit a WordPress plugin's REST surface and produce a standardized audit document proposing Abilities API registrations. Produces a markdown doc with a YAML schema and prose sections that humans and agents can both consume when planning a registration rollout. Works on any WP plugin.

Quality

72%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/wp-abilities-audit/SKILL.md

Quality

Content

77%

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

The content is a strong, well-sequenced instruction skill with explicit validation checkpoints and concrete actionable guidance, but two cross-skill reference paths are broken/absent and some prose could be tightened. Resolving the missing references would push progressive disclosure to the top level.

Suggestions

Resolve or remove the ../wp-abilities-api/references/grouping-heuristic.md and domain-vs-projection.md references — either inline the needed rules, make the paths resolve in the bundle, or clearly mark them as depending on a sibling skill that must be co-installed.

Tighten the intro and repeated "Read references/X.md now" phrasing, and condense the field-by-field exposition in step 4 where the schema reference already documents the shape.

Consider a short "Quick reference" line mapping each procedure step to its reference file so the overview stays lean while navigation remains explicit.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and avoids explaining basics Claude knows, but explanatory prose (intro paragraphs, repeated "Read references/X.md now" phrasing, and elaborated field descriptions) could be tightened, so it is not a full 3.	2 / 3
Actionability	Guidance is concrete and specific — exact field lists, schema shapes, explicit per-step actions like "Trace each controller's permission_callback to its current_user_can() call" — which is fully actionable even without code blocks; the scoring notes do not penalize absence of code in instruction-only skills.	3 / 3
Workflow Clarity	A clear 7-step procedure is paired with a dedicated Verification checklist (schema conformance, capability_gate shape, backing:null→surfaced_gaps, validator round-trip) and a Failure-modes/debugging section providing explicit validation checkpoints and feedback loops.	3 / 3
Progressive Disclosure	Local references are well-signaled and one level deep (references/controller-enumeration.md, audit-schema.md, capability-gate-tracing.md all exist), but two referenced cross-skill paths (../wp-abilities-api/references/grouping-heuristic.md and domain-vs-projection.md) do not exist in the bundle checkout, so navigation is not fully reliable and it falls short of 3.	2 / 3
	Total	10 / 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 well-differentiated with concrete actions and a clear niche, but it omits any "when to use" trigger guidance and leans on technical jargon rather than natural user phrasing. Adding a "Use when..." clause with common trigger terms would raise the completeness and trigger dimensions.

Suggestions

Append a "Use when..." clause stating when to invoke the skill (e.g. registering Abilities API abilities for a WP plugin, planning a multi-plugin abilities rollout, or pre-flight checking agent-readiness).

Surface natural trigger terms users would actually say — "WordPress plugin", "abilities", "REST endpoints", "audit" — alongside the technical jargon so the skill matches conversational phrasing.

Trim the inner mechanics ("YAML schema and prose sections", "humans and agents can both consume") in favor of a tighter what+when statement.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions — "Audit a WordPress plugin's REST surface", "produce a standardized audit document", "proposing Abilities API registrations", and "markdown doc with a YAML schema and prose sections" — matching the multi-action anchor.	3 / 3
Completeness	It clearly answers "what" but provides no "when"/"Use when" trigger guidance; per the judging guidelines a missing explicit trigger clause caps completeness at 2, ruling out 3.	2 / 3
Trigger Term Quality	Relevant keywords appear ("WordPress plugin", "WP plugin", "abilities", "audit") but the language is jargon-heavy ("REST surface", "Abilities API registrations", "YAML schema") with no natural "Use when" phrasing or common variations, so it is not a full 3.	2 / 3
Distinctiveness Conflict Risk	The niche is narrow and specific — auditing a WP plugin's REST surface for Abilities API registration — making it clearly distinguishable and unlikely to trigger for the wrong skill.	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-audit/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.