CtrlK
BlogDocsLog inGet started
Tessl Logo

wp-rest-api

Use when building, extending, or debugging WordPress REST API endpoints/routes: register_rest_route, WP_REST_Controller/controller classes, schema/argument validation, permission_callback/authentication, response shaping, register_rest_field/register_meta, or exposing CPTs/taxonomies via show_in_rest.

75

Quality

93%

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

86%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, lean procedure body that offloads detail to six real reference files and packs in WP-specific gotchas. It loses a little actionability (no full code example) and workflow granularity (verification is a trailing block rather than per-step checkpoints).

Suggestions

Add one complete, copy-paste register_rest_route() example with args/permission_callback/response in step 2 so the common case is fully executable.

Fold a brief inline verification checkpoint (e.g. hit /wp-json/ and OPTIONS) directly after route registration rather than only in the trailing Verification section.

Consider a short validation retry loop in step 3 for invalid-params cases to make the feedback loop explicit within the procedure.

DimensionReasoningScore

Conciseness

The body is almost entirely dense, actionable bullets with WP-specific facts Claude does not reliably know (e.g. 'per_page is capped at 100', '?context=edit for content.raw', '_doing_it_wrong for missing permission_callback'); no padding or explanations of REST/WordPress basics.

5 / 5

Actionability

Names concrete functions, constants, and callbacks (WP_REST_Server::READABLE/CREATABLE, rest_ensure_response, WP_Error with status) plus an executable triage command, but lacks a complete copy-paste register_rest_route code example covering the common case.

4 / 5

Workflow Clarity

A clearly numbered 0–6 procedure with a dedicated Verification section and Failure modes debugging list, but validation checkpoints live in a trailing section rather than inline after each step, leaving minor gaps.

4 / 5

Progressive Disclosure

Lean overview that signals one-level-deep references at the end of each section (custom-content-types, routes-and-endpoints, schema, responses-and-fields, authentication, discovery-and-params); all six referenced files exist and bulk detail is offloaded to them.

5 / 5

Total

18

/

20

Passed

Description

100%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 tight, third-person description that pairs an explicit 'Use when' trigger with a comprehensive list of concrete WP REST API capabilities and function names. It clears every dimension without padding or over-claiming.

DimensionReasoningScore

Specificity

Lists many concrete actions and API primitives — 'register_rest_route', 'WP_REST_Controller/controller classes', 'schema/argument validation', 'permission_callback/authentication', 'response shaping', 'register_rest_field/register_meta', 'exposing CPTs/taxonomies via show_in_rest' — giving comprehensive coverage of the domain.

5 / 5

Completeness

Explicit 'Use when...' clause supplies the trigger, and the colon-delimited list supplies the concrete 'what'; both are present with concrete trigger phrases, matching the 5 anchor.

5 / 5

Trigger Term Quality

Includes both natural phrases ('WordPress REST API endpoints/routes', 'building, extending, or debugging') and the exact function/constant names developers say aloud ('register_rest_route', 'WP_REST_Controller', 'permission_callback', 'show_in_rest'), with synonyms (endpoints/routes).

5 / 5

Distinctiveness Conflict Risk

The narrow WordPress REST API niche plus specific function names make it clearly distinguishable from sibling WP skills with minimal overlap risk.

5 / 5

Total

20

/

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.