wordpress
/wordpress
Manage WordPress on xCloud sites — list/update/activate plugins and themes, check WordPress health and update summaries, toggle WP_DEBUG, generate magic-login URLs, run vulnerability scans and manage findings (per site and team-wide), run PageSpeed Insights scans, and scan for broken links. Use for WordPress app management, "which sites need updates", security scans, PageSpeed scores, or broken links. Why a site is slow → xcloud:performance; a site throwing errors → xcloud:troubleshoot. For SSL see xcloud:ssl; for site backups/domains/cache see xcloud:sites; for server infra see xcloud:servers
- Author
- xclouddev ↗
- Repository
- xcloud-agent-skills ↗
- Licence
- MIT
- Last repository change
- 25.09.2026
Assessment and security
- Files in this package
- 6
- Scripts
- 1
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 25.09.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
- 1 scripts in this package. Review them before installing, as Claude may execute them.
Scripts: tests/smoke.sh
What it does and when to use it
Manage WordPress on xCloud sites — list/update/activate plugins and themes, check WordPress health and update summaries, toggle WP_DEBUG, generate magic-login URLs, run vulnerability scans and manage findings (per site and team-wide), run PageSpeed Insights scans, and scan for broken links. Use for WordPress app management, "which sites need updates", security scans, PageSpeed scores, or broken links. Why a site is slow → xcloud:performance; a site throwing errors → xcloud:troubleshoot. For SSL see xcloud:ssl; for site backups/domains/cache see xcloud:sites; for server infra see xcloud:servers
Triggers from the description
Original author description
Manage WordPress on xCloud sites — list/update/activate plugins and themes, check WordPress health and update summaries, toggle WP_DEBUG, generate magic-login URLs, run vulnerability scans and manage findings (per site and team-wide), run PageSpeed Insights scans, and scan for broken links. Use for WordPress app management, "which sites need updates", security scans, PageSpeed scores, or broken links. Why a site is slow → xcloud:performance; a site throwing errors → xcloud:troubleshoot. For SSL see xcloud:ssl; for site backups/domains/cache see xcloud:sites; for server infra see xcloud:servers
How it works
- Response format
- Sub-resources (load on demand)
- Core endpoints
- Examples
- Fleet questions
- Cross-domain note
- Pitfalls
SKILL.md preview
---
name: wordpress
description: Manage WordPress on xCloud sites — list/update/activate plugins and themes, check WordPress health and update summaries, toggle WP_DEBUG, generate magic-login URLs, run vulnerability scans and manage findings (per site and team-wide), run PageSpeed Insights scans, and scan for broken links. Use for WordPress app management, "which sites need updates", security scans, PageSpeed scores, or broken links. Why a site is slow → xcloud:performance; a site throwing errors → xcloud:troubleshoot. For SSL see xcloud:ssl; for site backups/domains/cache see xcloud:sites; for server infra see xcloud:servers.
---
# xCloud WordPress
> **Packaged REST boundary (v4.4.2):** `xcloud.sh` enforces GET-only requests with no body and has no write override. Non-GET examples below describe upstream API operations, not executable commands for this fallback. For mutations, use the corresponding connected xCloud MCP tool only after the required concrete user approval and server confirmation. If that tool/confirmation is unavailable, stop and direct the user to the dashboard; do not bypass this boundary with direct curl, SDKs, alternate scripts or by editing the wrapper. Configure REST credentials with read-only scopes.
Owns WordPress app management plus site vulnerability scanning, PageSpeed, and
broken-link scans.
Read the shared layer first for auth, base URL, and conventions:
- `${CLAUDE_PLUGIN_ROOT}/reference/auth.md`
- `${CLAUDE_PLUGIN_ROOT}/reference/conventions.md`
- `${CLAUDE_PLUGIN_ROOT}/reference/mcp.md` — **prefer the MCP tools when
connected**: `sites_wordpress_*` (plugins/themes/updates/status/update/
activate/refresh), `sites_vulnerabilities_*`, `vulnerabilities_index`
(team-wide), `sites_pagespeed_*`, `sites_broken-links_*`, `sites_wp-debug`,
`sites_magic-login`;
the `$XC` calls below are the REST fallback.
```bash
XC="${CLAUDE_PLUGIN_ROOT}/scripts/xcloud.sh"
```
Scopes: reads need `read:sites`, writes need `write:sites`.
## Response format
Brand every user-facing reply (see `reference/conventions.md` →
**Response format**): open with `☁️ **xCloud · WordPress** — <site domain>`, give
the trimmed result, and close with a `_via xcloud:wordpress_` line.
Narrate each call (see **Progress narration**): before every `$XC` call print one
line of what xCloud is doing, e.g. `☁️ xCloud is scanning \`<domain>\` for
vulnerabilities…`; the first call of a task opens with
`☁️ xCloud is starting a session…`. **Every progress line and every action
sentence must start with `xCloud` as the actor — never a bare verb like
"Scanning…" or "Updating…". Say `xCloud is scanning…`.**
On the **first** xcloud reply in a conversation, lead with the xCloud startup
banner (see `reference/conventions.md` → **Startup banner**) in a fenced code
block — once per conversation.
## Sub-resources (load on demand)
| Sub-resource | Reference file |
|---|---|
| Plugins, themes, updates, activate, refresh | `reference/plugins-themes.md` |
| Vulnerabilities (scan, list, ignore) | `reference/vulnerabilities.md` |
| PageSpeed Insights | `reference/pagespeed.md` |
| Broken links (scan, poll, findings) | `reference/broken-links.md` |
## Core endpoints
| Operation | Method + path |
|---|---|
| WP health status | `GET /sites/{uuid}/wordpress/status` |
| Updates summary | `GET /sites/{uuid}/wordpress/updates` |
| Toggle WP_DEBUG | `POST /sites/{uuid}/wp-debug` |
| Magic login URL | `POST /sites/{uuid}/magic-login` |
**Not here:** SSL → `xcloud:ssl`; backups/domains/cache/SSH → `xcloud:sites`;
server infra → `xcloud:servers`.
## Examples
WordPress health + pending updates:
```bash
SITE_UUID='replace-me'
"$XC" GET "/sites/$SITE_UUID/wordpress/status" | jq '.data'
"$XC" GET "/sites/$SITE_UUID/wordpress/updates" | jq '.data'
```
Toggle WP_DEBUG (`enabled` required):
```bash
"$XC" POST "/sites/$SITE_UUID/wp-debug" '{"enabled":true}' | jq '.message'
```
Generate a one-time admin magic-login URL:
```bash
"$XC" POST "/sites/$SITE_UUID/magic-login" '{"login_as":"admin"}' | jq -r '.data.url // .data'
```
## Fleet questions
"Which of my sites have pending core, plugin or theme updates?" → list sites
(`xcloud:sites`), keep the WordPress ones, read each one's updates summary, and
answer grouped by site with counts; offer to update the ones the user picks
(back up first — `reference/plugins-themes.md`). For vulnerabilities across the
team, `GET /vulnerabilities` answers in one call — sort worst first.
## Cross-domain note
`vulnerabilities` and `pagespeed` are addressed at `/sites/{uuid}/…` and work on
any site, but are owned here because they are predominantly WordPress concerns.
A non-WordPress "scan my site" request still routes here via the `xcloud:sites`
cross-link.
## Pitfalls
- Plugin/theme updates and activations are async and can optionally back up
first — see `reference/plugins-themes.md`.
- Magic-login URLs are single-use and expire after about ten minutes; treat them
like passwords, never log them. The first call on a site installs the
magic-login plugin over SSH, which is why it is confirm-gated on MCP.
Files in this package (6)
- SKILL.md 5 KB
- reference/broken-links.md 2 KB
- reference/pagespeed.md 2 KB
- reference/plugins-themes.md 2 KB
- reference/vulnerabilities.md 2 KB
- tests/smoke.sh 2 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · xclouddev/xcloud-agent-skills | 100 | MIT |
| ericrisco/rsc-harness | 100 | MIT |
| AceDataCloud/Skills | 100 | Apache-2.0 |
| TerminalSkills/skills | 100 | Apache-2.0 |
| G1Joshi/Agent-Skills | 100 | MIT |
| pingqLIN/skill-0 | 100 | MIT |
| ar4mirez/samuel | 100 | MIT |
| frontman-ai/frontman | 81 | Apache-2.0 |
Database snapshot: 13.11.2026 · package version 0e4f9e543856 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100ssl
SSL certificates and HTTPS for xCloud sites — view, list, install (Let's Encrypt / custom / Cloudflare), renew, check status, and delete certificates. Use for any cert or HTTPS request on a site. NOT general site lifecycle (see xcloud:sites), NOT WordPress updates or… - 100sites
Manage existing xCloud sites — list/inspect sites, status, events, deployment logs, monitoring and uptime history, backups (including Docker app backups and schedules), rescue, snapshots, staging environments, domains & redirections, cache purge, SSH/SFTP config, site cron jobs,… - 90wp-admin
WordPress site administration through the MCP Adapter. Use when the user asks to "check site status", "manage users", "update settings", "check plugins", "review site health", "manage comments", "check WordPress version", "list users", "change site settings", "manage menus",… - 90wordpress-maintenance-ops
Use when maintaining a WordPress site: updates, health checks, backups, plugin and theme hygiene. - 100pressable
Manage Pressable WordPress hosting via API. Use when creating/cloning sites, managing backups, purging cache, updating PHP versions, managing plugins, checking site status, or any Pressable hosting operations. - 98wp-migration
Migrate a WordPress site from local dev to live hosting, or sync content between environments. Use when the user asks to move, deploy or sync a WordPress site.