wp-wpcli-and-ops▌
wordpress/agent-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
WordPress operations and automation via WP-CLI with safe search-replace, database management, and multisite support.
- ›Covers search-replace for domain migrations, database export/import, plugin/theme/user management, cron inspection, and cache flushing
- ›Includes built-in guardrails: environment confirmation, dry-run validation, and backup workflows before destructive operations
- ›Supports multisite operations with site-specific ( --url ) and network-wide ( --network ) targeting
- ›Enable
WP-CLI and Ops
When to use
Use this skill when the task involves WordPress operational work via WP-CLI, including:
wp search-replace(URL changes, domain migrations, protocol switch)- DB export/import, resets, and inspections (
wp db *) - plugin/theme install/activate/update, language packs
- cron event listing/running
- cache/rewrite flushing
- multisite operations (
wp site *,--url,--network) - building repeatable scripts (
wp-cli.yml, shell scripts, CI jobs)
Inputs required
- Where WP-CLI will run (local dev, staging, production) and whether it’s safe to run.
- How to target the correct site root:
--path=<wordpress-root>and (multisite)--url=<site-url>
- Whether this is multisite and whether commands should run network-wide.
- Any constraints (no downtime, no DB writes, maintenance window).
Procedure
0) Guardrails: confirm environment and blast radius
WP-CLI commands can be destructive. Before running anything that writes:
- Confirm environment (dev/staging/prod).
- Confirm targeting (path/url) so you don’t hit the wrong site.
- Make a backup when performing risky operations.
Read:
references/safety.md
1) Inspect WP-CLI and site targeting (deterministic)
Run the inspector:
node skills/wp-wpcli-and-ops/scripts/wpcli_inspect.mjs --path=<path> [--url=<url>]
If WP-CLI isn’t available, fall back to installing it via the project’s documented tooling (Composer, container, or system package), or ask for the expected execution environment.
2) Choose the right workflow
A) Safe URL/domain migration (search-replace)
Follow a safe sequence:
wp db export(backup)wp search-replace --dry-run(review impact)- Run the real replace with appropriate flags
- Flush caches/rewrite if needed
Read:
references/search-replace.md
B) Plugin/theme operations
Use wp plugin * / wp theme * and confirm you’re acting on the intended site (and network) first.
Read:
references/packages-and-updates.md
C) Cron and queues
Inspect cron state and run individual events for debugging rather than “run everything blindly”.
Read:
references/cron-and-cache.md
D) Multisite operations
Multisite changes can affect many sites. Always decide whether you’re operating:
- on a single site (
--url=), or - network-wide (
--network/ iterating sites)
Read:
references/multisite.md
3) Automation patterns (scripts + wp-cli.yml)
For repeatable ops, prefer:
wp-cli.ymlfor defaults (path/url, PHP memory limits)- shell scripts that log commands and stop on error
- CI jobs that run read-only checks by default
Read:
references/automation.md
Verification
- Re-run
wpcli_inspectafter changes that could affect targeting or config. - Confirm intended side effects:
- correct URLs updated
- plugins/themes in expected state
- cron/caches flushed where needed
- If there’s a health check endpoint or smoke test suite, run it after ops changes.
Failure modes / debugging
- “Error: This does not seem to be a WordPress installation.”
- wrong
--path, wrong container, or missingwp-config.php
- wrong
- Multisite commands affecting the wrong site
- missing
--urlor wrong URL
- missing
- Search-replace causes unexpected serialization issues
- wrong flags or changing serialized data unsafely
See:
references/debugging.md
Escalation
- If you cannot confirm environment safety, do not run write operations.
- If the repo uses containerized tooling (Docker/wp-env) but you can’t access it, ask for the intended command runner or CI job.
How to use wp-wpcli-and-ops on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add wp-wpcli-and-ops
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches wp-wpcli-and-ops from GitHub repository wordpress/agent-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate wp-wpcli-and-ops. Access the skill through slash commands (e.g., /wp-wpcli-and-ops) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★58 reviews- ★★★★★Valentina Diallo· Dec 28, 2024
We added wp-wpcli-and-ops from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Emma Bhatia· Dec 24, 2024
I recommend wp-wpcli-and-ops for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Chaitanya Patil· Dec 16, 2024
Useful defaults in wp-wpcli-and-ops — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Yuki Iyer· Dec 16, 2024
Keeps context tight: wp-wpcli-and-ops is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Sophia Abbas· Nov 19, 2024
Keeps context tight: wp-wpcli-and-ops is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Zara Tandon· Nov 15, 2024
Solid pick for teams standardizing on skills: wp-wpcli-and-ops is focused, and the summary matches what you get after install.
- ★★★★★Piyush G· Nov 7, 2024
wp-wpcli-and-ops has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Hiroshi Martin· Nov 7, 2024
We added wp-wpcli-and-ops from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Shikha Mishra· Oct 26, 2024
Solid pick for teams standardizing on skills: wp-wpcli-and-ops is focused, and the summary matches what you get after install.
- ★★★★★Evelyn Abebe· Oct 26, 2024
wp-wpcli-and-ops fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 58