Skip to content
TrustedSkillsbeta
Back to all skills

Wp Rest Api

Official
automattic·vlatest·backend

Helps with REST APIs, API as part of developing backend services and APIs workflows.

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add automattic/agent-skills --skill wp-rest-api -a claude-code
  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

automattic

Matched to the vendor's own GitHub organisation.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned automattic/agent-skills at 48d4aa21d0.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Scanned
7 files, 267 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill assists with developing and debugging WordPress REST API integrations. It enables AI agents to create, update, and troubleshoot REST routes/endpoints within a WordPress environment. The skill focuses on tasks like adding custom fields to responses, exposing custom post types, implementing data validation, and adjusting pagination settings for APIs.

When to use it

  • Creating or updating REST endpoints in a WordPress project.
  • Debugging common REST API errors such as 401, 403, or 404 issues, including permission and nonce problems.
  • Adding custom fields or metadata to the data returned by REST API responses.
  • Exposing custom post types or taxonomies through the WordPress REST API.
  • Adjusting response links, embedding options, or pagination behavior for APIs.

Key capabilities

  • Creating and updating REST routes using register_rest_route().
  • Implementing schema and argument validation.
  • Adding custom fields/meta to REST responses using register_rest_field and register_meta.
  • Exposing custom post types or taxonomies via the WordPress REST API (using show_in_rest).
  • Adjusting response links with WP_REST_Response::add_link().

Example prompts

  • "Create a new REST endpoint under the 'my-plugin/v1' namespace to retrieve user data."
  • "Debug why I am receiving a 403 error when accessing my custom REST route."
  • "Add a custom field called 'featured_image_url' to the response for posts accessed via the /wp/v2/posts endpoint."

Tips & gotchas

  • The skill requires knowledge of WordPress development and REST API principles.
  • When working with full site repositories, ensure you are modifying code within the correct plugin or theme.
  • Always use a unique namespace (e.g., vendor/v1) for custom endpoints to avoid conflicts.