WordPress站点设置与连接配置指南：WP-CLI与REST API完整教程

wordpress-setup by jezweb/claude-skills

349 周安装量

650 GitHub Stars

GitHub

安装命令

npx skills add https://github.com/jezweb/claude-skills --skill wordpress-setup

自动化开发运维 WordPress

🇨🇳中文介绍

WordPress 设置

连接到 WordPress 站点，并通过 WP-CLI 或 REST API 验证工作访问权限。生成一个经过验证的连接配置，用于内容管理和 Elementor 编辑。

工作流程

步骤 1：检查 WP-CLI

wp --version

如果未安装，引导用户：

# macOS/Linux
curl -O https://raw.githubusercontent.com/wp-cli/builds/gh-pages/phar/wp-cli.phar
chmod +x wp-cli.phar
sudo mv wp-cli.phar /usr/local/bin/wp

同时确保 SSH 扩展可用（远程站点需要）：

wp package install wp-cli/ssh-command

步骤 2：连接到站点

选项 A：通过 SSH 使用 WP-CLI（推荐）

wp --ssh=user@hostname/path/to/wordpress option get siteurl

常见模式：

Rocket.net: wp --ssh=user@hostname/www/sitename/public option get siteurl
cPanel: wp --ssh=user@hostname/public_html option get siteurl

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

步骤 3：存储凭据

对于 WP-CLI SSH — 在项目根目录创建一个 wp-cli.yml：

ssh:
  sitename:
    cmd: ssh -o StrictHostKeyChecking=no %pseudotty% user@hostname %cmd%
    url: /path/to/wordpress

然后使用：wp @sitename option get siteurl

对于 REST API — 存储在 .dev.vars 中：

WP_SITE_URL=https://example.com
WP_USERNAME=admin
WP_APP_PASSWORD=xxxx xxxx xxxx xxxx xxxx xxxx

确保 .dev.vars 在 .gitignore 中。对于跨项目使用，请存储在你偏好的密码管理器中（环境变量、1Password CLI 等）。

步骤 4：验证完全访问权限

运行全面检查：

# 站点信息
wp @sitename option get siteurl
wp @sitename option get blogname

# 内容访问
wp @sitename post list --post_type=page --posts_per_page=5 --fields=ID,post_title,post_status

# 插件状态（检查 Elementor）
wp @sitename plugin status elementor

# 主题信息
wp @sitename theme status

步骤 5：保存站点配置

创建 wordpress.config.json 供其他技能引用：

{
  "site": "example.com",
  "siteUrl": "https://example.com",
  "accessMethod": "ssh",
  "sshAlias": "sitename",
  "wpPath": "/path/to/wordpress",
  "hasElementor": true,
  "elementorVersion": "3.x.x"
}

症状	修复方法
`Permission denied (publickey)`	检查 SSH 密钥：`ssh -v user@host`
通过 SSH 出现 `wp: command not found`	远程 PATH 中没有 WP-CLI — 使用完整路径：`/usr/local/bin/wp`
`Error: This does not appear to be a WordPress installation`	路径错误 — 检查 `wp-path` 参数
大型操作超时	添加 `--ssh=user@host/path --allow-root` 或增加 SSH 超时时间

在 ~/.wp-cli/config.yml 中为经常访问的站点定义别名：

@client1:
  ssh: user@client1.example.com/www/public
@client2:
  ssh: user@client2.rocketcdn.me/www/client2/public

然后使用：wp @client1 post list

REST API 注意事项

应用程序密码需要 HTTPS（在 HTTP 上不起作用）
某些安全插件会阻止 REST API — 检查 401/403 响应
缓存插件可能提供过时的 REST 响应 — 使用 ?_=${timestamp} 缓存清除器
自定义文章类型需要在 API 中显示 show_in_rest: true

references/wp-cli-essentials.md — SSH 别名模式、常用标志和故障排除

🇺🇸English

WordPress Setup

Connect to a WordPress site and verify working access via WP-CLI or REST API. Produces a verified connection config ready for content management and Elementor editing.

Workflow

Step 1: Check WP-CLI

wp --version

If not installed, guide the user:

# macOS/Linux
curl -O https://raw.githubusercontent.com/wp-cli/builds/gh-pages/phar/wp-cli.phar
chmod +x wp-cli.phar
sudo mv wp-cli.phar /usr/local/bin/wp

Also ensure the SSH extension is available (needed for remote sites):

wp package install wp-cli/ssh-command

Step 2: Connect to the Site

Option A: WP-CLI over SSH (preferred)

wp --ssh=user@hostname/path/to/wordpress option get siteurl

Common patterns:

Rocket.net: wp --ssh=user@hostname/www/sitename/public option get siteurl
cPanel: wp --ssh=user@hostname/public_html option get siteurl
Custom: Ask user for SSH user, host, and WordPress path

Test with a simple command first:

wp --ssh=user@host/path core version

Option B: REST API with Application Password

If SSH isn't available:

Navigate to https://example.com/wp-admin/profile.php (or use browser automation)
Scroll to "Application Passwords" section
Enter a name (e.g. "Claude Code") and click "Add New Application Password"
Copy the generated password (spaces are part of it but optional in auth)

Test the connection:

curl -s https://example.com/wp-json/wp/v2/posts?per_page=1 \
  -u "username:xxxx xxxx xxxx xxxx xxxx xxxx" | jq '.[0].title'

Step 3: Store Credentials

For WP-CLI SSH — create a wp-cli.yml in the project root:

ssh:
  sitename:
    cmd: ssh -o StrictHostKeyChecking=no %pseudotty% user@hostname %cmd%
    url: /path/to/wordpress

Then use: wp @sitename option get siteurl

For REST API — store in .dev.vars:

WP_SITE_URL=https://example.com
WP_USERNAME=admin
WP_APP_PASSWORD=xxxx xxxx xxxx xxxx xxxx xxxx

Ensure .dev.vars is in .gitignore. For cross-project use, store in your preferred secrets manager (environment variable, 1Password CLI, etc.).

Step 4: Verify Full Access

Run a comprehensive check:

# Site info
wp @sitename option get siteurl
wp @sitename option get blogname

# Content access
wp @sitename post list --post_type=page --posts_per_page=5 --fields=ID,post_title,post_status

# Plugin status (check for Elementor)
wp @sitename plugin status elementor

# Theme info
wp @sitename theme status

Step 5: Save Site Config

Create wordpress.config.json for other skills to reference:

{
  "site": "example.com",
  "siteUrl": "https://example.com",
  "accessMethod": "ssh",
  "sshAlias": "sitename",
  "wpPath": "/path/to/wordpress",
  "hasElementor": true,
  "elementorVersion": "3.x.x"
}

Critical Patterns

SSH Connection Issues

Symptom	Fix
`Permission denied (publickey)`	Check SSH key: `ssh -v user@host`
`wp: command not found` via SSH	WP-CLI not in remote PATH — use full path: `/usr/local/bin/wp`
`Error: This does not appear to be a WordPress installation`	Wrong path — check `wp-path` argument
Timeout on large operations	Add `--ssh=user@host/path --allow-root` or increase SSH timeout

WP-CLI Aliases

Define aliases in ~/.wp-cli/config.yml for frequently-accessed sites:

@client1:
  ssh: user@client1.example.com/www/public
@client2:
  ssh: user@client2.rocketcdn.me/www/client2/public

Then: wp @client1 post list

REST API Gotchas

Application passwords require HTTPS (won't work on HTTP)
Some security plugins block REST API — check for 401/403 responses
Caching plugins may serve stale REST responses — use ?_=${timestamp} cache buster
Custom post types need show_in_rest: true to appear in API

Reference Files

references/wp-cli-essentials.md — SSH alias patterns, common flags, and troubleshooting

Weekly Installs

335

Repository

jezweb/claude-skills

GitHub Stars

643

First Seen

Feb 22, 2026

Security Audits

Gen Agent Trust HubWarn SocketPass SnykFail

Installed on

codex304

gemini-cli303

opencode303

github-copilot302

amp301

kimi-cli301

Azure Data Explorer (Kusto) 查询技能：KQL数据分析、日志遥测与时间序列处理

100,500 周安装