WordPress WP-CLI Admin

核心功能涵盖WordPress健康检查、插件与主题管理、用户及内容操作、核心版本维护、数据库迁移、多站点管理等。适用于具备shell/SSH访问权限的WordPress站点运维，不可用于仅HTTP访问环境或自定义WP-CLI命令开发。操作需遵循先检查再执行的工作流，优先读操作，避免无备份的危险写操作，通过shell命令输入，返回对应执行结果。

matthewxmurphy

热度 79.46

最近更新 2026-05-11 17:28:41

分类：自动化依赖：代码执行 / 读写文件应用场景：DevOps / 自动化脚本 / 数据处理 / 任务管理

安装技能

复制下面的话术发给你的 Agent，它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill： npx secure-skills-cli add wordpress-wp-cli-admin

Metadata

name: wordpress-wp-cli-admin
description: Operate WordPress installs through WP-CLI for inspection, core maintenance, plugin and theme management, users, options, content, media, cron, database tasks, and multisite-aware administration. Use when shell, SSH, or node-local access exists and the task should be done with `wp` instead of the REST API or custom WP-CLI package development.
metadata: {"openclaw":{"emoji":"🛠️"}}

WordPress WP-CLI Admin

Use this skill when a WordPress task belongs in wp, not /wp-json.

The point of this skill is not to memorize every command. The point is to get to the right command family, attach the right global flags, inspect the target install first, and avoid reckless write operations.

Use This Skill For

checking whether a target install is healthy and reachable with wp
plugin and theme management
users, roles, comments, posts, pages, terms, and media operations
options, transients, rewrites, cron, and cache-related site work
core version, update, checksum, and maintenance tasks
database export, import, and search-replace work
multisite-aware administration when --url matters

Do Not Use This Skill For

REST-only integrations where the caller has HTTP access but not shell access
building custom WP-CLI commands or packages
blind destructive operations without a read-first pass or backup path

Workflow

1. Inspect The Install First

Start with:

scripts/inspect-install.sh --path /srv/www/site
scripts/inspect-install.sh --path /srv/www/site --url https://example.com

This checks that wp exists, confirms the path looks like a WordPress install, and prints useful status for core, URLs, plugins, and themes.

If you need the live command tree:

scripts/list-commands.sh
scripts/list-commands.sh --group plugin

2. Choose The Right Command Family

Read references/command-families.md.

Default mapping:

core health or updates: core
installed code: plugin, theme, language
content and taxonomy: post, page, comment, term, category, tag
accounts and permissions: user, role, cap, super-admin
config and runtime: option, transient, cron, rewrite, cache
database and migration: db, search-replace
multisite: site, network, super-admin

3. Attach The Right Global Flags

Read references/global-flags-and-safety.md.

Common flags:

--path=<path>
--url=<url>
--user=<login>
--ssh=<target>
--http=<url>
--skip-plugins
--skip-themes
--debug
--quiet
--format=json

4. Prefer Read-First Commands

Examples:

wp plugin list --format=table
wp theme list --format=table
wp option get home
wp core version
wp cron event list

Only then move to write operations such as plugin update, search-replace, option update, or db import.

5. Treat High-Risk Operations As Change Windows

Before destructive work:

export the database
use search-replace --dry-run when available
verify the target URL in multisite
avoid running broad updates without confirming versions and dependencies

Files

scripts/inspect-install.sh: inspect a target WordPress path with WP-CLI
scripts/list-commands.sh: print wp help or wp help <group> for live command discovery
references/command-families.md: command family cheat sheet for common WordPress admin tasks
references/global-flags-and-safety.md: global arg patterns, remote execution, and destructive-operation rules