Install
$ agentstack add skill-sarai-chinwag-wp-openclaw-wp-openclaw-setup ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ● Network access Used
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
WP-OpenClaw Setup Skill
Purpose: Help a user install wp-openclaw on a remote VPS from their local machine.
This skill is for the local agent (Claude Code, etc.) assisting with installation. Once OpenClaw is running on the VPS, this skill is no longer needed — the OpenClaw agent takes over with its own pre-loaded skills.
FIRST: Interview the User
Do NOT proceed with installation until you've asked these questions and gotten answers.
Question 1: Installation Type
> "Are you setting up a fresh WordPress site, or do you have an existing WordPress site you want to add OpenClaw to?"
Options:
- Fresh install — New VPS, new WordPress site
- Existing WordPress — Site already running, just add OpenClaw
- Migration — Site exists elsewhere, moving to this VPS
Question 2: Autonomous Operation
> "Do you want autonomous operation capabilities? This includes Data Machine — a self-scheduling system that lets your agent set reminders, queue tasks, and operate 24/7 without human intervention. > > - Yes (recommended for content sites) — Full autonomy, self-scheduling, proactive operation > - No (simpler setup) — Agent responds when asked, no self-scheduling overhead"
Question 3: Server Details
> "I'll need some details about your server: > 1. What's the server IP address? > 2. Do you have SSH access? (key or password) > 3. What domain will this site use?"
Question 4: For Existing WordPress
If they chose existing WordPress:
> "Where is WordPress installed on the server? (e.g., /var/www/mysite)"
Build the Command
Based on their answers, construct the appropriate command:
| Scenario | Command | |----------|---------| | Fresh + Data Machine | SITE_DOMAIN=example.com ./setup.sh | | Fresh, no Data Machine | SITE_DOMAIN=example.com ./setup.sh --no-data-machine | | Existing + Data Machine | EXISTING_WP=/var/www/mysite ./setup.sh --existing | | Existing, no Data Machine | EXISTING_WP=/var/www/mysite ./setup.sh --existing --no-data-machine |
Add --skip-deps if nginx, PHP, MySQL, Node are already installed. Add --skip-ssl to skip Let's Encrypt certificate. Add --secure to run the agent as a non-root user.
Confirm Before Proceeding
Before running anything, summarize what you're about to do:
> "Here's the plan: > - Server: 123.45.67.89 > - Domain: example.com > - Type: Fresh install > - Data Machine: Yes > - Command: SITE_DOMAIN=example.com ./setup.sh > > Does this look right?"
Only continue after explicit confirmation.
Run via SSH
ssh root@
git clone https://github.com/Sarai-Chinwag/wp-openclaw.git
cd wp-openclaw
For migration, first transfer the database and wp-content:
# On old server
mysqldump dbname > backup.sql
tar -czf wp-content.tar.gz -C /var/www/oldsite wp-content/
scp backup.sql wp-content.tar.gz root@newserver:/tmp/
# On new server — import, then run setup with --existing
mysql -e "CREATE DATABASE wordpress;" && mysql wordpress < /tmp/backup.sql
mkdir -p /var/www/mysite && tar -xzf /tmp/wp-content.tar.gz -C /var/www/mysite/
The script handles everything: PHP (auto-detected), dependencies, WordPress, Data Machine, nginx, SSL, OpenClaw, skills, and workspace files.
Post-Setup Verification
After setup.sh completes, verify:
# WordPress
wp --allow-root option get siteurl
# Data Machine (if installed)
wp --allow-root plugin list | grep data-machine
# OpenClaw
openclaw gateway status
# Site reachable
curl -I https://yourdomain.com
Then complete OpenClaw configuration:
openclaw configure # Set up API keys and channels
systemctl start openclaw # Start the agent
Credentials are saved to ~/.openclaw/credentials (chmod 600).
When to Use This Skill
Use when the user says things like:
- "Help me install OpenClaw on my server"
- "Set up wp-openclaw on this VPS"
- "Add OpenClaw to my existing WordPress site"
Do NOT use for ongoing WordPress management — that's the OpenClaw agent's job after installation.
Troubleshooting
- WordPress 500 errors: Check PHP-FPM status, nginx error log, file permissions
- WP-CLI errors: Use
--allow-root, verify wp-config.php - OpenClaw won't start: Check
node --version(needs 18+), check~/.openclaw/logs/ - Data Machine not working: Verify plugin active, run
wp action-scheduler run --allow-root
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Sarai-Chinwag
- Source: Sarai-Chinwag/wp-openclaw
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.