Lean bullet-driven body that assumes Claude's competence; it does not explain what WordPress or WP-CLI is, and warnings like 'WP-CLI commands can be destructive' are justified guardrails rather than padding.

Provides concrete executable commands (e.g. 'wp db export', 'wp search-replace --dry-run', 'wp cache flush', 'wp rewrite flush') and a runnable inspector invocation 'node skills/wp-wpcli-and-ops/scripts/wpcli_inspect.mjs --path=<path>', with reference files supplying full command lists.

Clearly sequenced Procedure (steps 0–3) with explicit validation checkpoints — environment/targeting guardrails, a --dry-run review step before destructive replaces, and a Verification section that re-runs wpcli_inspect — providing feedback loops for destructive ops.

Overview body points via well-signaled 'Read:' cues to seven verified one-level-deep reference files, with content appropriately split by topic and easy navigation; no deep nesting.

Lists multiple concrete actions/domains — 'safe search-replace, db export/import, plugin/theme/user/content management, cron, cache flushing, multisite, and scripting/automation with wp-cli.yml' — matching the 'lists multiple specific concrete actions' anchor.

Explicit 'Use when working with WP-CLI (wp) for WordPress operations' trigger plus a clear enumeration of what it does, answering both what and when.

Covers natural terms a user would say — 'WP-CLI', 'wp', 'WordPress', 'search-replace', 'db export/import', 'plugin/theme', 'cron', 'multisite', 'wp-cli.yml' — with good coverage rather than just jargon.

A clear WP-CLI/WordPress-ops niche with distinct triggers unlikely to fire for other skills; not generic enough to conflict.