CtrlK
BlogDocsLog inGet started
Tessl Logo

wp-abilities-api

Use when working with the WordPress Abilities API (wp_register_ability, wp_register_ability_category, /wp-json/wp-abilities/v1/*, @wordpress/abilities) including defining abilities, categories, meta, REST exposure, and permissions checks for clients.

72

Quality

88%

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%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.

A well-structured instructional skill: clear multi-step workflow with verification and failure modes, and excellent progressive disclosure through well-signaled reference files. Slight verbosity in a few preamble sentences and the relocation of executable PHP into references keep it just short of maximal conciseness and actionability.

Suggestions

Tighten the inline prose before each `references/*.md` pointer to one clause so the body stays a pure index of decisions.

Inline a minimal copy-paste `wp_register_ability(...)` + init-hook skeleton so the body is executable without opening php-registration.md.

Add a one-line note in the Consume-from-JS step naming the specific @wordpress/abilities function to call, mirroring the concreteness of the PHP steps.

DimensionReasoningScore

Conciseness

Largely efficient and assumes Claude's competence, but a few explanatory sentences (e.g. the domain-vs-projection and shared-core-service preamble paragraphs) could be trimmed without losing the actionable pointer.

4 / 5

Actionability

Provides concrete searchable strings, named init hooks, and specific meta flags (readonly, show_in_rest), though the executable PHP registration code itself lives in referenced files rather than inline.

4 / 5

Workflow Clarity

A clear numbered six-step sequence is paired with a Verification section and a Failure modes / debugging section that act as explicit checkpoints and feedback loops.

5 / 5

Progressive Disclosure

The body is a well-organized overview pointing to nine one-level-deep reference files, each clearly signaled inline at the decision point where it is needed; references are real and easy to navigate.

5 / 5

Total

18

/

20

Passed

Description

92%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, specific description that names concrete capabilities and the API surface alongside an explicit "Use when..." trigger. Minor room to add plain-language synonyms alongside the technical identifiers.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "defining abilities, categories, meta, REST exposure, and permissions checks" — with named API surface, giving comprehensive coverage rather than vague abstractions.

5 / 5

Completeness

Explicitly answers both what (defining abilities, categories, meta, REST exposure, permissions checks) and when ("Use when working with the WordPress Abilities API...") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong keyword coverage including natural terms ("WordPress Abilities API") plus technical identifiers (wp_register_ability, /wp-json/wp-abilities/v1/*, @wordpress/abilities), though it lacks plain synonyms like "client capabilities" or "ability registration".

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (WordPress Abilities API) with distinct, specific triggers unlikely to fire for unrelated skills.

5 / 5

Total

19

/

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.

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.