Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
OpenClaw skill that provides a WordPress REST API CLI for posts, pages, categories, tags, users, and custom requests using plain HTTP.
OpenClaw skill that provides a WordPress REST API CLI for posts, pages, categories, tags, users, and custom requests using plain HTTP.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Provide a production-ready CLI for WordPress REST API automation. This skill focuses on content workflows (posts/pages), taxonomy (categories/tags), user reads, and safe custom requests without external HTTP libraries.
You want a stable CLI for automation and bot workflows. You need JSON-in/JSON-out for pipelines. You prefer simple HTTP with no extra dependencies.
You must handle OAuth flows or complex browser-based auth. You need advanced media uploads (multipart streaming).
Node.js 18+ (for native fetch).
Enable the WordPress REST API (default in modern WordPress). Create an Application Password for a WordPress user. Confirm the user has the right role (e.g., Editor/Admin).
cd wordpress npm install
node scripts/wp-cli.js help node scripts/wp-cli.js posts:list --query per_page=5 node scripts/wp-cli.js posts:create '@post.json' You can also use npm: npm run wp -- posts:list --query per_page=5
Supported options (first match wins): Basic auth token: WP_BASIC_TOKEN (base64 of user:app_password) User + app password: WP_USER + WP_APP_PASSWORD JWT bearer token: WP_JWT_TOKEN
WP_BASE_URL (e.g., https://example.com)
JSON can be inline or loaded from file with @path. Query params use --query key=value (repeatable) or --query key1=value1,key2=value2.
Posts: posts:list, posts:get, posts:create, posts:update, posts:delete Pages: pages:list, pages:get, pages:create, pages:update, pages:delete Taxonomy: categories:list, categories:create tags:list, tags:create Users: users:list, users:get Advanced: request (raw method + path)
Prefer context=view for read-only list calls. Use status=draft when staging content. Implement retries for 429 and transient 5xx errors in orchestrators.
JSON to stdout; non-zero exit code on errors.
Never log or commit tokens or application passwords. Use a dedicated low-privilege WordPress account where possible.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.