Wp Local Env
Use when the user wants to work with a local WordPress development environment — WordPress Studio, LocalWP, or wp-env. Handles environment detection, site lifecycle, WP-CLI proxy, REST API access, symlink workflows, database operations, and preview/share.
Install
npx skills add morrealev/wordpress-manager --skill wp-local-envgit clone --depth 1 https://github.com/morrealev/wordpress-manager.git /tmp/wordpress-manager
mkdir -p ~/.claude/skills
cp -r /tmp/wordpress-manager/skills/wp-local-env ~/.claude/skills/wp-local-envPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Local WordPress Environment ## When to use Use this skill when the task involves local WordPress development environments: - Detecting which local dev tool is installed (Studio, LocalWP, wp-env) - Creating, starting, stopping, or deleting local WordPress sites - Running WP-CLI commands against a local site - Setting up plugin/theme development via symlinks - Accessing the local REST API or database - Switching PHP/WordPress versions for testing - Previewing or sharing a local site externally - Preparing a local site for deployment to production ## Inputs required - Whether the user has WordPress Studio, LocalWP, or wp-env (auto-detected) - The site to operate on (name, path, or auto-detected from current directory) - The desired operation (lifecycle, development, testing, deploy prep) ## Procedure ### 0) Detect local environments Run the detection script to discover installed tools and sites: ```bash node skills/wp-local-env/scripts/detect_local_env.mjs ``` The script outputs JSON with: - `environments[]` — each tool found with its sites - `recommended` — which tool to prefer for automation - `wpCli` — how to invoke WP-CLI for each tool If no environment is found, suggest installation: - **WordPress Studio** (lightweight, fast): https://developer.wordpress.com/studio/ - **LocalWP** (production-parity): https://localwp.com/ - **wp-env** (Docker-based, for contributors): `npm -g install @wordpress/env` ### 1) Site lifecycle #### Create a new local site
Details
- Skill name
wp-local-env- Repository
- morrealev/wordpress-manager
- Path
skills/wp-local-env/SKILL.md- Repo updated
- 2 March 2026
FAQ
What does the Wp Local Env skill do?
Use when the user wants to work with a local WordPress development environment — WordPress Studio, LocalWP, or wp-env. Handles environment detection, site lifecycle, WP-CLI proxy, REST API access, symlink workflows, database operations, and preview/share.
How do I install the Wp Local Env skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add morrealev/wordpress-manager --skill wp-local-env. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Wp Local Env popular?
It lives in morrealev/wordpress-manager, which has 9 GitHub stars and 1 forks.
Related skills
Wordpress Router
9morrealev/wordpress-manager
“Use when the user asks about WordPress — whether development (plugins, themes, blocks, REST API) or operations (deploy, audit, backup, migrate, content management). Classifies the task and routes to the correct development or operational skill/agent.”
Wp Accessibility
9morrealev/wordpress-manager
Use when improving WordPress accessibility: block accessibility (ARIA, keyboard navigation), theme accessibility (landmarks, skip links, color contrast), interactive component accessibility, media accessibility (alt text, captions, transcripts), and automated/manual a11y testing with WCAG 2.2 compliance.
Wp Alerting
9morrealev/wordpress-manager
This skill should be used when the user asks about "alerting", "alerts", "Slack notifications", "email alerts", "monitoring alerts", "threshold alerts", "health reports", "escalation", "incident notifications", "uptime alerts", "error alerts", "performance alerts", "scheduled reports", or mentions setting up notification channels for WordPress monitoring events.
Auto Scope
9borkweb/skills
Scopes a coding task before implementation — names the handful of files actually relevant (read/edit these), the areas to leave alone, and any open scope questions, so work doesn't start by reading the whole repo. Fires proactively at the start of substantive, multi-file, or unfamiliar-area work; stays silent on single-file edits, one-line fixes, questions, and continued work in an area already scoped this session. Use when beginning a feature, bug fix, or refactor that could plausibly touch several files or an area not yet seen this session.
Wp I18n
9morrealev/wordpress-manager
Use when internationalizing WordPress plugins or themes: PHP gettext functions (__/esc_html__/etc.), JavaScript i18n (@wordpress/i18n), .pot/.po/.mo translation workflow, WP-CLI i18n commands, RTL stylesheet support, and multilingual plugin setup (Polylang/WPML).
Cmd Clean Code
9Olshansk/agent-skills
Improve code readability without altering functionality using idiomatic best practices
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.