Skills wp-wpcli-and-ops

📦

wp-wpcli-and-ops

Name: wp-wpcli-and-ops
Author: Automattic

Content revision r2 Safe ⚙️ External commands

Manage WordPress Safely with WP-CLI

WordPress command-line operations can damage data or affect the wrong site. This skill provides guarded workflows for inspection, changes, automation, and verification.

Supports: Claude Codex Code(CC)

🥈 81 Silver

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "wp-wpcli-and-ops" from https://skillstore.io/skills/automattic-wp-wpcli-and-ops.md and its manifest at https://skillstore.io/api/skills/automattic-wp-wpcli-and-ops/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/automattic-wp-wpcli-and-ops.md Signed manifest GET /api/skills/automattic-wp-wpcli-and-ops/manifest Signed lockfile GET /api/skills/automattic-wp-wpcli-and-ops/lockfile

Test it

Using "wp-wpcli-and-ops". Inspect the staging site before a URL migration.

Expected outcome:

WP-CLI is available, and WordPress is detected at the requested path.
The site is a single installation with matching home and site URLs.
Next step: export the database before previewing URL replacements.

Using "wp-wpcli-and-ops". Plan production plugin updates without downtime.

Expected outcome:

List installed plugins and available updates before selecting targets.
Confirm backups, maintenance timing, and plugin-specific compatibility requirements.
Update selected plugins individually, then run health checks and review logs.

Using "wp-wpcli-and-ops". Diagnose a multisite command affecting the wrong site.

Expected outcome:

Confirm the WordPress root and intended site URL.
Use site-specific targeting for one site and network targeting only with explicit approval.
Repeat the inspection before running the corrected command.

Security Audit

Safe

v11 • 7/23/2026 Open versioned report

All 34 static findings are false positives after contextual review. The script intentionally runs fixed, read-only WP-CLI inspections without a shell, while the remaining matches are documentation formatting and safety guidance.

Files scanned

406

Lines analyzed

Review items

False positives ignored

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/automattic-wp-wpcli-and-ops/audits/11?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/automattic-wp-wpcli-and-ops/security.svg)](https://skillstore.io/skills/automattic-wp-wpcli-and-ops?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/automattic-wp-wpcli-and-ops?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/automattic-wp-wpcli-and-ops/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/automattic-wp-wpcli-and-ops.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

Automattic. (2026). wp-wpcli-and-ops security audit report (audit version 11) [Author version unspecified]. Skillstore. https://skillstore.io/skills/automattic-wp-wpcli-and-ops/audits/11

BibTeX citation

@techreport{automattic-automattic-wp-wpcli-and-ops-2026,
  author = {Automattic},
  title = {wp-wpcli-and-ops security audit report (audit version 11)},
  institution = {Skillstore},
  year = {2026},
  number = {11},
  url = {https://skillstore.io/skills/automattic-wp-wpcli-and-ops/audits/11},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "wp-wpcli-and-ops security audit report (audit version 11)"
version: "unspecified"
type: report
authors:
  - name: "Automattic"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/automattic-wp-wpcli-and-ops/audits/11"
identifiers:
  - type: other
    value: "skillstore:automattic-wp-wpcli-and-ops:audit:11"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Migrate a WordPress Site

Prepare backups, preview URL replacements, apply scoped changes, and verify the migrated site.

Maintain Production Sites

Review updates, cron events, caches, and site health with production guardrails.

Operate WordPress Multisite

Choose site-specific or network-wide targeting before running repeatable maintenance tasks.

Try These Prompts

Inspect a WordPress Site

Inspect the WordPress site at [path] using WP-CLI. Report its version, multisite status, URLs, and targeting problems. Do not make changes.

Plan Plugin and Theme Updates

Plan updates for [site] in [environment]. List current package state, identify production risks, and require confirmation before any write operation.

Prepare a Domain Migration

Prepare a migration from [old domain] to [new domain]. Include backup, dry-run, scope, multisite, cache, rollback, and verification steps.

Design Multisite Automation

Design a repeatable WP-CLI workflow for [task] across [sites]. Add logging, per-site isolation, failure handling, explicit apply controls, and post-run verification.

Best Practices

Confirm environment, WordPress root, site URL, and multisite scope before write operations.
Create a database backup and use dry-run options before broad data changes.
Verify URLs, package state, caches, cron behavior, and application health after changes.

Avoid

Do not run bulk updates or destructive database commands on production without explicit confirmation.
Do not assume the current directory or default URL targets the intended site.
Do not automate write operations without logging, failure handling, and an explicit apply control.