Operate WordPress installs through WP-CLI for inspection, core maintenance, plugin and theme management, users, options, content, media, cron, database tasks...
文档
WordPress WP-CLI Internal API
试用Build, inspect, and extend WP-CLI command code using the documented stable internal API. Use when the task involves custom WP-CLI commands, package bootstrap...
它能做什么
Build, inspect, and extend WP-CLI command code using the documented stable internal API. Use when the task involves custom WP-CLI commands, package bootstrap...
技能文档
WordPress WP-CLI Internal API
Use this skill when you are writing WP-CLI itself, not merely operating WordPress through wp.
The official internal API reference exposes a stable surface for command registration, logging, hooks, execution, and output formatting. This skill keeps that stable surface close at hand and gives you a quick command skeleton generator.
Use This Skill For
- building custom WP-CLI commands
- reviewing command classes that call
WP_CLI::add_command() - choosing between
WP_CLI::log(),success(),warning(), anderror() - formatting output with
WP_CLI\Utils\format_items() - running one WP-CLI command from another with
WP_CLI::runcommand() - using hooks such as
WP_CLI::add_hook()andWP_CLI::do_hook()
Do Not Use This Skill For
- normal site administration where a stock WP-CLI command already exists
- REST route implementation or review
- plugin business logic that has nothing to do with WP-CLI command entrypoints
Workflow
1. Stay On The Stable Surface
Read references/stable-internal-api.md.
Start from the officially documented stable methods instead of undocumented internals.
2. Render A Command Skeleton
Use:
scripts/render-command-skeleton.sh --command acme report --class Acme_Report_Command
scripts/render-command-skeleton.sh --command acme report --class Acme_Report_Command --write /tmp/report-command.php
This gives you a minimal command class that already uses:
WP_CLI::add_command()WP_CLI::success()WP_CLI\Utils\get_flag_value()WP_CLI\Utils\format_items()
3. Choose Output And Error Patterns Deliberately
Read references/command-patterns.md.
Default rule:
- human progress:
log()orline() - successful completion:
success() - non-fatal concern:
warning() - fatal stop:
error()
4. Prefer Internal Execution Helpers Over Shelling Out
If a command needs to trigger another WP-CLI command, prefer:
WP_CLI::runcommand()WP_CLI::launch_self()
Reach for generic shell execution only when the task is truly outside WP-CLI.
Files
scripts/render-command-skeleton.sh: render a minimal custom command class and registration stubreferences/stable-internal-api.md: grouped stable API surface from the official WP-CLI internal API docsreferences/command-patterns.md: practical command-authoring patterns and guardrails
相关技能
Work with the WordPress REST API for route discovery, authentication, reads and writes, core endpoint selection, and custom namespace inspection. Use when a...
Read and write WordPress.com site content through WordPress.com's hosted MCP server. Thin pass-through to WordPress.com's official MCP; the live tool catalog...
通过 REST API 管理 WordPress 内容,带显式审批、批量演练与插件/CPT 工具支持。
通过 WP-CLI 审计、清理与调优 WordPress 站点,覆盖数据库、自动加载、慢查询与前端。
Use when operating the installed `whoop` CLI for agent-friendly WHOOP access, cross-platform secret storage checks, daily briefs, summaries, health flags, ac...