RepoAI
Browse MCPs

WP Playground

94TrustedInstructions only

WordPress Playground routing for CLI, browser-based, and remote debugging workflows.

What it does

Wp Playground functions as a primary routing hub for your WordPress development environments. It allows the assistant to distinguish between browser-based interactive sessions and command-line execution, ensuring the correct technical approach is applied to your specific infrastructure needs.

By keeping this skill as a central router, the assistant maintains clean boundaries between different development environments. It handles the nuances of transient, SQLite-powered instances while directing more granular concerns—such as specific configuration syntax or debugging logs—to their specialized reference modules.

When it earns its place

Reach for it when…

Use this skill when you need to switch between local CLI testing and browser-hosted prototypes, or when you encounter runtime issues in a Playground session that require specific debugging flags or environment adjustments.

Look elsewhere when…

Do not use this skill for drafting or validating JSON blueprints, as these tasks belong to the dedicated blueprint skill. It is also unsuitable for persistent, production-grade hosting environments that require standard MySQL databases rather than SQLite.

What to say to use it

You never invoke a skill directly — the assistant picks it up when your request matches what it covers. These are the kinds of things that do that.

  • help me debug my wordpress playground session
  • run a local wordpress site using playground cli
  • how do i share a wordpress playground link
  • switch wordpress and php versions in my playground instance

Install it

Install for all your projects

Copy the skill directory into your personal skills folder. Claude picks it up on its own the next time your request matches what it does — there is nothing to enable.

bash
git clone --depth 1 --branch trunk https://github.com/WordPress/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/wp-playground ~/.claude/skills/wp-playground

Install for one project only

Put it in the project's own skills folder instead, so it can be committed and shared with everyone working on that repository.

bash
cp -r /tmp/agent-skills/skills/wp-playground .claude/skills/wp-playground

If a skill of the same name exists in both places, the personal one wins.

Installing on Claude.ai or through the API instead? The full guide covers every surface.

Pair it with an MCP server

WP Playground changes how the work is done. These servers change what Claude can reach while doing it.

How skills and MCP servers differ →