Agent skill
wordpress-content-manager
WordPress content management via REST API for listing, searching, viewing, creating, updating, and deleting posts (including draft/scheduled/published) with tags and categories. Use when managing WordPress blog content, especially for blog.gbase.com or other sites configured via profiles. Requires Node.js and WordPress REST API credentials.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/design/wordpress-content-manager-jakenuts-agent-skills
Metadata
Additional technical details for this skill
- requires setup
- YES
- default profile
- gbase-blog
SKILL.md
WordPress Content Manager
Manage WordPress posts in a site-agnostic way. This skill defaults to the Gbase blog profile but supports multiple site profiles.
Stage 1: Copy Only (No Install)
Ensure these are present on the target machine/container:
- This skill folder (copied by agent-skills deploy scripts)
- The WordPress CLI tool folder from
X:\core\tools\blog-wordpress
Do not install Node or npm packages at this stage.
Stage 2: Lazy Runtime Setup (Non-Interactive)
Run the setup script the first time the skill is activated. It verifies Node, installs dependencies, and validates access.
Windows (PowerShell)
pwsh ~/.codex/skills/wordpress-content-manager/scripts/setup.ps1
Linux/macOS
bash ~/.codex/skills/wordpress-content-manager/scripts/setup.sh
If you are using Claude Code, replace ~/.codex/skills with ~/.claude/skills.
Profiles and Site Selection
Profiles live under profiles/ in this skill. Select a profile with:
--profile <name>flag- or
WP_PROFILE=<name>env var
If neither is set, the default profile gbase-blog is used.
See references/profiles.md for the profile format and overrides.
Required Environment Variables
WP_USERNAME(WordPress username)WP_APP_PASSWORD(WordPress Application Password)
Optional overrides:
WP_API_URLWP_SITE_URLWP_CLI_PATH(path toblog-wordpressCLI folder)
Commands
All commands are non-interactive and return JSON when --json is set.
Describe Connection
node ~/.codex/skills/wordpress-content-manager/scripts/wp-content.mjs site info --json
List or Search Posts
node ~/.codex/skills/wordpress-content-manager/scripts/wp-content.mjs posts list --status publish --search "guitar" --per_page 20 --page 1
View a Post
node ~/.codex/skills/wordpress-content-manager/scripts/wp-content.mjs posts get 123 --json
Create a Post (HTML or Markdown)
node ~/.codex/skills/wordpress-content-manager/scripts/wp-content.mjs posts create \
--title "New Post" \
--content-file ./post.md \
--status draft \
--categories 1,2 \
--tags 5,7
Schedule a Post
node ~/.codex/skills/wordpress-content-manager/scripts/wp-content.mjs posts create \
--title "Scheduled Post" \
--content "<p>HTML body</p>" \
--status future \
--date "2025-01-15T15:30:00"
Update a Post
node ~/.codex/skills/wordpress-content-manager/scripts/wp-content.mjs posts update 123 \
--title "Updated Title" \
--status publish
Delete a Post
node ~/.codex/skills/wordpress-content-manager/scripts/wp-content.mjs posts delete 123
Bulk Delete (Dry-Run First)
node ~/.codex/skills/wordpress-content-manager/scripts/wp-content.mjs posts delete-many \
--status draft \
--search "test" \
--dry-run
node ~/.codex/skills/wordpress-content-manager/scripts/wp-content.mjs posts delete-many \
--status draft \
--search "test" \
--confirm
Future Extensions (Out of Scope for v1)
- Plugin management
- YouTube automation or auto-content plugins
These can be added in a future version or by wrapping a more full-featured WordPress admin tool.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?