WordPress Expert

For people (what am I getting?)

What this skill is

• A pack of instructions and checklists for your OpenClaw agent so it can work with a WordPress site you already have—content, settings, media, plugins, themes, WooCommerce, Elementor, and development under wp-content.
• The agent reaches WordPress over HTTPS (REST) and, when you configure it, WP-CLI and scoped file access on the machine where the OpenClaw gateway runs.

Strong recommendation: install the companion OpenClaw plugin

You should install the companion plugin wordpress-site-tools on the OpenClaw gateway host (clone → npm install → openclaw plugins install → enable → allow tools → gateway restart). That plugin registers typed, policy-aware tools (wordpress_rest_request, wordpress_wp_cli, wordpress_connection_check, optional media upload and plugin file access). The skill is written to prefer those tools over hand-built curl/exec—they are clearer, easier to audit, and easier to allowlist.

• The skill works without that plugin only via documented fallbacks (exec, curl, browser)—more manual and easier to get wrong; use only if you consciously skip the plugin.
• Before npm install / enable: skim the public source on GitHub and read {baseDir}/references/PRE_INSTALL_AND_TRUST.md (staging, least privilege, secrets in config not chat).

Full steps: {baseDir}/README.md, {baseDir}/references/CONNECTING.md.

OpenClaw surfaces this recommendation twice: the YAML description is what the gateway includes in the compact skill list shown to the model; metadata.openclaw.homepage is the Website link in OpenClaw’s Skills UI (docs)—here it points at the plugin repository so users land on install/source without extra clicks.