How do I install the Wordpress Wp CLI Internal API skill?

Run npx skillmds@latest add dvcrn/wordpress-wp-cli-internal-api in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Wordpress Wp CLI Internal API safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: executes scripts. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Wordpress Wp CLI Internal API?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Wordpress Wp CLI Internal API free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Wordpress Wp CLI Internal API?

dvcrn (@dvcrn) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Wordpress Wp CLI Internal API by dvcrn

Name: Wordpress Wp CLI Internal API
Rating: 4.2 (5 reviews)
Author: dvcrn

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 bootstraps, command registration, hooks, output helpers, internal execution helpers, or PHP code that calls `WP_CLI::*` or `WP_CLI\\Utils::*`.

dvcrn Updated Sep 8, 2026 32 repo stars

File contents

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(), and error()
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() and WP_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() or line()
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 stub
references/stable-internal-api.md: grouped stable API surface from the official WP-CLI internal API docs
references/command-patterns.md: practical command-authoring patterns and guardrails

---name: wordpress-wp-cli-internal-apidescription: Build, inspect, and extend WP-CLI command code using the documented stable internal API. Use when the task involves custom WP-CLI commands, package bootstraps, command registration, hooks, output helpers, internal execution helpers, or PHP code that calls `WP_CLI::*` or `WP_CLI\\Utils::*`.---# WordPress WP-CLI Internal APIUse 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()`, and `error()`- 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()` and `WP_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 SurfaceRead [references/stable-internal-api.md](references/stable-internal-api.md).Start from the officially documented stable methods instead of undocumented internals.### 2. Render A Command SkeletonUse:```bashscripts/render-command-skeleton.sh --command acme report --class Acme_Report_Commandscripts/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 DeliberatelyRead [references/command-patterns.md](references/command-patterns.md).Default rule:- human progress: `log()` or `line()`- successful completion: `success()`- non-fatal concern: `warning()`- fatal stop: `error()`### 4. Prefer Internal Execution Helpers Over Shelling OutIf 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 stub- `references/stable-internal-api.md`: grouped stable API surface from the official WP-CLI internal API docs- `references/command-patterns.md`: practical command-authoring patterns and guardrails

Frequently asked questions