WordPress Copilot

What it does

WordPress Copilot manages content and site administration through WordPress’s built-in REST API. It begins with a read-only scan so it understands the active theme, plugins, content types, taxonomies, custom fields, permissions, and the REST surfaces the connected account can actually reach.

You ask for the outcome in plain English. The skill translates that request into the relevant WordPress operation, reads the current value before changing it, preserves the site’s existing content model, verifies the result, and records the completed change in the site’s local changelog.

When to reach for it

Use it when the work belongs in wp-admin but the route through wp-admin is repetitive, scattered across screens, or easy to get wrong: page copy, posts, categories, media, supported SEO fields, users, and custom content on an existing site.

Do not reach for it to write theme or plugin code, change the database, deploy files, install or update plugins, migrate a site, or configure the server.

Prerequisites

• Claude Code on macOS, Windows, or Linux; or the Claude desktop app / Cowork
• WordPress 5.6 or newer
• A WordPress administrator or editor account
• Permission to create a revocable WordPress Application Password
• Python 3 on macOS/Linux for the read-only scan; Windows uses the PowerShell scan path
• Desktop / Cowork only: the site domain added under Settings → Capabilities before setup

Claude web and mobile do not provide the filesystem access this workflow needs.

How it works

1. 01

   Install the skill

   Run the public GitHub install command in a terminal. It adds the skill globally to Claude Code. Claude / Cowork can use the upload-compatible ZIP.

2. 02

   Ask for setup

   Open Claude in the site folder or mapped Cowork project and say: “Set up my WordPress access.”

3. 03

   Connect the site

   The skill collects the site URL and WordPress login name, verifies reachability, and guides you through creating a separate Application Password.

4. 04

   Map what is actually available

   A read-only scan records the active theme and plugins, content types, taxonomies, and REST capabilities before any later write.

5. 05

   Ask for the real outcome

   Describe the edit in plain English. Low-risk single edits can run directly; broader or sensitive changes require confirmation.

Common requests

• “Fix the typo on my About page.”
• “Publish this post with its category, featured image, and SEO title.”
• “Find published posts with no meta description.”
• “Add alt text to media-library images that are missing it.”
• “Add this case study using the site’s existing fields and taxonomy.”
• “Show me who has administrator access.”
• “Rescan the site after the plugin change.”

What works depends on how the site exposes its content. The initial scan exists so the skill can say what is reachable here instead of guessing.

The boundary

It manages content. It does not touch code.

Credential safety

It's working if

• The initial scan is read-only and accurately describes what the connected account can reach.
• The skill reads the current value and recorded site capabilities before a write.
• Risky, multi-item, user-role, and site-wide changes are shown before they run.
• The first real edit lands in the correct content type without flattening structured data.
• The completed operation appears in the site’s readable changelog.
• Revoking the Application Password stops access without changing the main WordPress password.

Where it fits

WordPress Copilot owns recurring content and site-administration work on an existing site. When a request crosses into code, data migration, deployment, or infrastructure, it stops at the boundary and hands the work to a WordPress developer workflow.

The first prompt is setup. After the read-only scan, the normal loop is: ask for an outcome → inspect the current state → confirm if required → make the change → read it back → record it.

What changed