メニュー
Query WP Engine account data — sites, installs, usage metrics, bandwidth, visits, storage, domains, backups, SSL, users, and diagnostics. Use when asked about WPE environments, usage stats, storage, installs, traffic, or anything related to the WP Engine account.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Run WP-CLI commands on a local WordPress site via nexus. Target format is <sitename>@local. For WPE remote installs use nexus-wpe skill instead.
Search across all indexed local WordPress sites by content. Use when looking for sites that contain specific content, posts, or pages. Pass the search query as args.
Pull a WP Engine environment down to a local site — files and optionally database. Requires the local site to exist and be running. Use when you want to sync a WPE environment locally.
Push a local site up to a WP Engine environment. DESTRUCTIVE — overwrites the live WPE environment. Requires explicit confirmation. Use only when intentionally deploying local changes to WPE.
Set up AI features on a local WordPress site — installs the AI plugin, configures the provider, syncs credentials, and enables experiments. Use when onboarding a new local site for AI capabilities.
Run Nexus AI diagnostics. Checks Local running, addon active, MCP server, gateway, AI provider, API key, and site count. Auto-suggests the exact fix command for every failure. Use when troubleshooting Nexus or verifying a working setup.
| name | nexus-wpe |
| description | Query WP Engine account data — sites, installs, usage metrics, bandwidth, visits, storage, domains, backups, SSL, users, and diagnostics. Use when asked about WPE environments, usage stats, storage, installs, traffic, or anything related to the WP Engine account. |
Topic: $ARGUMENTS
nexus wpe portfolio
This shows all accounts, total installs, and fleet-wide visits + bandwidth. Use this data to answer usage/traffic/storage questions directly when possible. Only run additional commands if more detail is needed.
Based on $ARGUMENTS and what the portfolio output didn't cover:
| Topic | Command |
|---|---|
| Usage / bandwidth / visits (fleet) | ✅ Already in portfolio above |
| Usage drill-down (per account) | nexus wpe account-usage <accountId> |
| Usage drill-down (per install) | nexus wpe usage <installId> |
| Prior month usage | nexus wpe portfolio --month-offset 1 |
| Account overview | nexus wpe account <accountId> |
| Account limits | nexus wpe limits <accountId> |
| All installs for an account | nexus wpe installs <accountId> |
| Install details | nexus wpe install <installId> |
| Domains | nexus wpe domains <installId> |
| SSL status | nexus wpe ssl <installId> |
| Backups | nexus wpe backup-status <installId> <backupId> |
| Users | nexus wpe users <accountId> |
| Diagnose install | nexus wpe diagnose <installId> |
| Go-live check | nexus wpe go-live-check <installId> <domain> |
If the portfolio shows zeros for visits/bandwidth, the current billing period
hasn't rolled up yet. Run: nexus wpe portfolio --month-offset 1 to get last month's data.