wp-rest-api 是做什麼的？
在建立、擴充或除錯 WordPress REST API 端點/路由時使用：register_rest_route、WP_REST_Controller/控制器類別、結構描述/參數驗證、permission_callback/身份驗證、回應塑形、register_rest_field/register_meta，或透過 show_in_rest 公開自訂文章類型/分類法。
在建立、擴充或除錯 WordPress REST API 端點/路由時使用：register_rest_route、WP_REST_Controller/控制器類別、結構描述/參數驗證、permission_callback/身份驗證、回應塑形、register_rest_field/register_meta，或透過 show_in_rest 公開自訂文章類型/分類法。
這個技能專為處理 WordPress REST API 的開發者而設計，涵蓋從路由註冊到回應塑形的完整生命週期。它支援透過 `register_rest_route` 定義自訂端點，使用 `WP_REST_Controller` 建立結構化的控制器類別，並確保透過結構描述和參數驗證進行嚴格的輸入處理。開發者可以利用 `permission_callback` 和身份驗證機制實作細粒度的存取控制，同時使用 `register_rest_field` 或 `register_meta` 將自訂欄位無縫附加到回應中。此外，該技能簡化了透過 `show_in_rest` 參數公開自訂文章類型 (CPT) 和分類法的過程，使其成為任何在 WordPress 生態系統中構建或除錯 API 端點之人的必備工具。它與所有主要的 AI 代理平台（如 Claude Code、Coder 和 Codex）相容，並透過提供針對 WordPress REST API 模式最佳化的結構化提示來運作。
npx skills add https://github.com/wordpress/agent-skills/tree/main/skills/wp-rest-apiInstalled? Explore more 生產力與協作 skills: steipete/gemini, steipete/gh-issues, steipete/skill-creator · View all 6 →
在建立、擴充或除錯 WordPress REST API 端點/路由時使用：register_rest_route、WP_REST_Controller/控制器類別、結構描述/參數驗證、permission_callback/身份驗證、回應塑形、register_rest_field/register_meta，或透過 show_in_rest 公開自訂文章類型/分類法。
This repo contains 13 individual skills — each has its own dedicated page.
Use when creating, editing, or reviewing WordPress Playground blueprint JSON files. Triggers on mentions of blueprints, playground configuration, or requests to set up a WordPress demo environment.
Use when the user asks about WordPress codebases (plugins, themes, block themes, Gutenberg blocks, WP core checkouts) and you need to quickly classify the repo and route to the correct workflow/skill (blocks, theme.json, REST API, WP-CLI, performance, security, testing, release packaging).
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.
Use when developing WordPress (Gutenberg) blocks: block.json metadata, register_block_type(_from_metadata), attributes/serialization, supports, dynamic rendering (render.php/render_callback), deprecations/migrations, viewScript vs viewScriptModule, and @wordpress/scripts/@wordpress/create-block build and test workflows.
Use when developing WordPress block themes: theme.json (global settings/styles), templates and template parts, patterns, style variations, and Site Editor troubleshooting (style hierarchy, overrides, caching).
Use when building UIs leveraging the WordPress Design System (WPDS) and its components, tokens, patterns, etc.
Use when building or debugging WordPress Interactivity API features (data-wp-* directives, @wordpress/interactivity store/state/actions, block viewScriptModule integration, wp_interactivity_*()) including performance, hydration, and directive behavior.
Use when investigating or improving WordPress performance (backend-only agent): profiling and measurement (WP-CLI profile/doctor, Server-Timing, Query Monitor via REST headers), database/query optimization, autoloaded options, object caching, cron, HTTP API calls, and safe verification.
Use when configuring, running, or fixing PHPStan static analysis in WordPress projects (plugins/themes/sites): phpstan.neon setup, baselines, WordPress-specific typing, and handling third-party plugin classes.
Use for WordPress Playground workflows: fast disposable WP instances in the browser or locally via @wp-playground/cli (server, run-blueprint, build-snapshot), auto-mounting plugins/themes, switching WP/PHP versions, blueprints, and debugging (Xdebug).
Use when developing WordPress plugins: architecture and hooks, activation/deactivation/uninstall, admin UI and Settings API, data storage, cron/tasks, security (nonces/capabilities/sanitization/escaping), and release packaging.
Use when you need a deterministic inspection of a WordPress repository (plugin/theme/block theme/WP core/Gutenberg/full site) including tooling/tests/version hints, and a structured JSON report to guide workflows and guardrails.
Use when working with WP-CLI (wp) for WordPress operations: safe search-replace, db export/import, plugin/theme/user/content management, cron, cache flushing, multisite, and scripting/automation with wp-cli.yml.
Gemini CLI one-shot prompts, summaries, generation, skills, hooks, MCP, or Gemma routing.
Fetch GitHub issues, select candidates, spawn background fix agents, open PRs, and optionally process PR review comments.
Create, edit, audit, tidy, validate, or restructure AgentSkills and SKILL.md files.
Search, install, update, sync, or publish agent skills with the ClawHub CLI and registry.
Delegate coding work to Codex, Claude Code, or OpenCode as background workers; not simple edits or read-only code lookup.
List, configure, authenticate, call, and inspect MCP servers/tools with mcporter over HTTP or stdio.