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. If not installed, guide the user: Also ensure the SSH extension is available (needed for remote sites): Option A: WP-CLI over SSH (preferred) Common patterns: Test with a simple command first: Option B: REST API with Application Password If SSH isn't available: Test the connection: For WP-CLI SSH — create a wp-cli.yml in the project root: Then use: wp @sitename option get siteurl For REST API — store in .dev.vars : Ensure .dev.vars is in .gitignore . For cross-project use, store in your preferred secrets manager (environment variable, 1Password CLI, etc.). Run a comprehensive check: Create wordpress.config.json for other skills to reference: Define aliases in ~/.wp-cli/config.yml for frequently-accessed sites: Then: wp @client1 post list - 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 - Navigate to (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) - Application passwords require HTTPS (won't...