fix: drop requirements.txt from ClawHub payload (v3.5.1)

CHANGELOG.md

@@ -1,5 +1,12 @@
 # Changelog
 
+## 3.5.1 - 2026-06-01
+
+ClawHub packaging compatibility.
+
+- Removed `wordpress-api-pro/requirements.txt` from the published skill payload — the ClawHub package directory ships only `.json` / `.md` / `.py` / `.sh` files, so the single `.txt` is dropped to keep publishing clean.
+- The `requests` dependency (ACF / SEO / JetEngine / plugin-detection scripts only) is now installed directly: `pip install requests`. `INSTALL.sh`, README, and SKILL.md updated accordingly. Core scripts remain stdlib-only.
+
 ## 3.5.0 - 2026-06-01
 
 Claude Code support.

INSTALL.sh

@@ -51,8 +51,8 @@ if [ -d "$DEST" ]; then
 fi
 
 mkdir -p "$DEST"
-# Copy the payload contents (SKILL.md, scripts/, references/, config/, wp.sh,
-# requirements.txt) to the skill root so relative `scripts/*.py` paths resolve.
+# Copy the payload contents (SKILL.md, scripts/, references/, config/, wp.sh)
+# to the skill root so relative `scripts/*.py` paths resolve.
 cp -R "$SRC"/. "$DEST"/
 chmod +x "$DEST/wp.sh" 2>/dev/null || true
 ok "Installed skill payload"
@@ -63,8 +63,8 @@ if python3 -c "import requests" >/dev/null 2>&1; then
   ok "'requests' already available"
 else
   warn "'requests' not installed. Install it when you need the plugin scripts:"
-  printf "      ${CYAN}python3 -m pip install -r \"$DEST/requirements.txt\"${RESET}\n"
-  printf "    ${DIM}(or use a venv: python3 -m venv .venv && .venv/bin/pip install -r requirements.txt)${RESET}\n"
+  printf "      ${CYAN}python3 -m pip install requests${RESET}\n"
+  printf "    ${DIM}(or use a venv: python3 -m venv .venv && .venv/bin/pip install requests)${RESET}\n"
 fi
 
 cat <<EOF

README.md

@@ -33,7 +33,7 @@ ClawHub package directory: `wordpress-api-pro/`.
 
 ## Version
 
-Current version: **3.5.0**
+Current version: **3.5.1**
 
 ## Installation
 
@@ -59,7 +59,7 @@ cd wordpress-api-pro
 bash INSTALL.sh
 ```
 
-Then restart Claude Code, export `WP_URL` / `WP_USERNAME` / `WP_APP_PASSWORD` (or set up `config/sites.json`), and ask Claude to use it. The ACF / SEO / JetEngine / plugin-detection scripts need `requests` (`pip install -r requirements.txt`); the core post/page/media/WooCommerce/batch scripts use the Python stdlib only.
+Then restart Claude Code, export `WP_URL` / `WP_USERNAME` / `WP_APP_PASSWORD` (or set up `config/sites.json`), and ask Claude to use it. The ACF / SEO / JetEngine / plugin-detection scripts need `requests` (`pip install requests`); the core post/page/media/WooCommerce/batch scripts use the Python stdlib only.
 
 > Pairs well with the [Elementor MCP kit](https://github.com/Digitizers/claude-elementor-pro): build pages with the MCP, then handle media uploads, SEO meta, custom fields, and WooCommerce with these scripts.
 

package.json

@@ -1,6 +1,6 @@
 {
   "name": "wordpress-api-pro",
-  "version": "3.5.0",
+  "version": "3.5.1",
   "description": "WordPress REST API integration skill for OpenClaw - manage posts, pages, media, WooCommerce, Elementor, and metadata with explicit safety boundaries",
   "private": true,
   "main": "wordpress-api-pro/SKILL.md",
@@ -53,7 +53,6 @@
     "wordpress-api-pro/references/**/*.md",
     "wordpress-api-pro/scripts/**/*.py",
     "wordpress-api-pro/wp.sh",
-    "wordpress-api-pro/requirements.txt",
     "INSTALL.sh",
     "README.md",
     "CHANGELOG.md",

wordpress-api-pro/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: wordpress-api-pro
-version: 3.5.0
+version: 3.5.1
 license: MIT-0
 description: |
   WordPress REST API integration for managing posts, pages, media, WooCommerce products, Elementor content, SEO meta, ACF, and JetEngine fields.
@@ -18,7 +18,7 @@ Manage WordPress sites through the REST API. Runs as an OpenClaw skill or in Cla
 This skill runs the `scripts/*.py` directly. From the skill directory (`~/.claude/skills/wordpress-api-pro/` after `bash INSTALL.sh`):
 
 - **Auth:** export `WP_URL` / `WP_USERNAME` / `WP_APP_PASSWORD`, or use `config/sites.json` for multi-site.
-- **Dependencies:** the ACF / SEO / JetEngine / plugin-detection scripts need `requests` (`python3 -m pip install -r requirements.txt`, ideally in a venv). The core post/page/media/WooCommerce/batch scripts use the stdlib only.
+- **Dependencies:** the ACF / SEO / JetEngine / plugin-detection scripts need `requests` (`python3 -m pip install requests`, ideally in a venv). The core post/page/media/WooCommerce/batch scripts use the stdlib only.
 - **Local dev sites** (e.g. `http://site.local`) work — the private/HTTP restriction applies only to `--allow-remote-url` media downloads, not the WP API base URL.
 - **Pairs with the Elementor MCP kit** (`claude-elementor-pro`): build page structure with the MCP, then do media uploads, SEO meta, custom fields, and WooCommerce here.