wordpress-content-manager

WordPress post management via REST API automates CRUD operations on posts across sites. Use this Skill to list, search, create, update, and delete posts with status control (draft, publish, scheduled) and tag/category assignment without manual API calls.

Yes, profile-driven configuration lets you manage posts across multiple WordPress sites. Each profile maps to a site configuration; switch targets with --profile or WP_PROFILE environment variable to operate on different sites.

WordPress content automation requires Node.js 16+, WP_USERNAME and WP_APP_PASSWORD environment variables for secure authentication, and optional WP_API_URL and WP_SITE_URL overrides. Credentials authenticate REST API requests without storing secrets in code.

Filter posts by status (draft, publish, future) and search by terms using --status and search parameters. The Skill returns JSON output with full post metadata, enabling category and tag-based filtering within non-interactive CLI workflows.

Yes, this Skill satisfies requirements for non-interactive CLI workflows. It accepts command-line parameters, reads credentials from environment variables, outputs JSON for downstream processing, and runs entirely headless—ideal for automation, cron jobs, and CI/CD pipelines.

REST API provides programmatic, network-based post management across sites with structured JSON I/O and profile switching. WordPress CLI runs locally on the server; REST API works remotely and integrates into Node.js automation workflows without WP_CLI_PATH dependency.