wordpress

What This Skill Does

The WordPress REST API skill provides a robust, developer-centric CLI for managing WordPress sites via OpenClaw. It serves as an interface for the native WordPress REST API, allowing users to perform CRUD operations on posts, pages, categories, tags, and users without needing a browser. By utilizing Node.js 18+ native fetch, it ensures a lightweight, dependency-minimal execution environment. It effectively bridges the gap between local automation scripts and remote WordPress site management, supporting JSON-based inputs and outputs, which makes it ideal for automated content pipelines and headless CMS architectures.

Installation

To install this skill, use the ClawHub CLI: clawhub install openclaw/skills/skills/codedao12/wordpress. Ensure you have Node.js 18 or higher installed on your machine. Once installed, navigate to the wordpress directory and run npm install. You must set your environment variables, specifically WP_BASE_URL, and provide authentication via WP_BASIC_TOKEN, WP_USER/WP_APP_PASSWORD, or a WP_JWT_TOKEN to enable authorized requests.

Use Cases

This skill is designed for scenarios requiring programmatic interaction with a WordPress instance. Common use cases include: automated content publishing (batch creating draft posts), synchronizing taxonomy (tags/categories) across staging and production sites, generating automated reports on user activity or post metadata, and performing bulk cleanup of content via scripting. It is perfect for developers who need to integrate WordPress into a larger CI/CD pipeline or for content managers who want to push updates from local JSON files directly to their CMS.

Example Prompts

1. "OpenClaw, use the wordpress skill to list the last 5 posts on my site and save them to a file named current_posts.json."
2. "Create a new draft post on the WordPress site using the content provided in local file './drafts/new_post.json'."
3. "List all categories currently defined in the WordPress system using the wordpress:categories:list command."

Tips & Limitations

When using this skill, always prefer using context=view for read-only operations to reduce load on your WordPress database. For critical operations, implement logic in your orchestrator to handle HTTP 429 (too many requests) and 5xx errors with exponential backoff. Note that this skill does not support complex OAuth flows or heavy multipart media uploads; for such tasks, it is recommended to use native WordPress XML-RPC or specialized media plugins. Always use application-specific passwords rather than master credentials to minimize security risks. Ensure the user associated with the Application Password has the minimum necessary permissions to perform the required actions, following the principle of least privilege.