/SKILL.md
Run WP-CLI commands against any Local by Flywheel site. Use when the user says 'wp-cli', 'run wp', 'use wp-cli', 'activate plugin', 'deactivate plugin', 'flush cache', 'wp option', 'wp transient', 'wp db', 'wp eval', 'wp cron', 'wp rewrite', or any request involving WordPress CLI commands.
npx skillsauth add aslamdoctor/local-wp-cli local-wp-cliInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Run all WP-CLI commands using the wrapper script bundled with this skill:
bash {{SKILL_DIR}}/scripts/wp <site-name> <command>
Never run bare wp commands. Always use the full path above.
The first argument is the Local site name (as shown in the Local app), followed by any WP-CLI command.
WP="bash {{SKILL_DIR}}/scripts/wp"
# Examples with different sites
$WP my-site plugin list
$WP my-site core version
$WP my-site user list
If the user doesn't specify a site name, ask them which Local site to use. You can run the script with no arguments to list available sites.
/usr/local/bin/wp)~/Library/Application Support/Local/sites.jsonWP="bash {{SKILL_DIR}}/scripts/wp"
SITE="my-site" # replace with actual site name
# Plugin management
$WP $SITE plugin list
$WP $SITE plugin activate <slug>
$WP $SITE plugin deactivate <slug>
$WP $SITE plugin status <slug>
# Cache / transients
$WP $SITE cache flush
$WP $SITE transient delete --all
# Options
$WP $SITE option get <key>
$WP $SITE option update <key> <value>
$WP $SITE option list --search="<pattern>"
# Database
$WP $SITE db query "SELECT * FROM wp_options WHERE option_name LIKE '<pattern>%' LIMIT 10;"
$WP $SITE db export backup.sql
$WP $SITE db import backup.sql
# Eval PHP
$WP $SITE eval 'echo get_option("siteurl");'
$WP $SITE eval-file script.php
# Rewrites / cron
$WP $SITE rewrite flush
$WP $SITE cron event list
$WP $SITE cron event run <hook>
# User / site info
$WP $SITE user list
$WP $SITE option get siteurl
$WP $SITE core version
tools
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.
tools
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------
tools
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------
tools
A CLI tool for making authenticated requests to the X (Twitter) API. Use this skill when you need to post tweets, reply, quote, search, read posts, manage followers, send DMs, upload media, or interact with any X API v2 endpoint.