All skills
wordpress avatar

/wp-playground

@e9c58d5 official
by wordpresswordpress/agent-skills2.2k stars
327

Use as the WordPress Playground routing wrapper for ambiguous Playground work, local CLI runs with @wp-playground/cli, playground.wordpress.net share links, browser previews, WebMCP site tools, snapshots, mounts, version switching, and Xdebug. For Blueprint JSON authoring or review, use the blueprint skill directly.

Use this Skill: https://skilld.dev/gh/wordpress/agent-skills/wp-playground

This session only. Nothing lands on disk.

referencesmcp.md

≈389 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Playground MCP

Use this reference when the user requests Playground MCP, or when the interaction router selects an available MCP connection as a fallback.

Connect to the intended site

Playground MCP uses a local MCP server and WebSocket bridge. Its website connection parameters are mcp=yes and optionally mcp-port=<port>; the default port is 7999. These parameters belong to Playground MCP, not WebMCP.

Prefer an existing connection targeting the intended site. Do not reload an existing tab, create a replacement site, or discard current work merely to enable the bridge. If a connection is unavailable, return to the interaction router for an available fallback; if the user requires MCP specifically, report the missing connection instead of silently changing methods.

Discover and call tools

  1. Inspect the tools exposed by the connected Playground MCP server and their descriptions and input schemas. Do not reuse WebMCP tool names or arguments without checking the MCP interface.
  2. Confirm that the connection targets the intended site with a harmless information/read operation before making changes.
  3. Use the available tool that supports the requested operation. If no suitable tool exists, return to the interaction router for a fallback consistent with the user's requested method.

Verification

Check tool results and verify the requested state through the same site connection before claiming success. Preserve the active browser site when switching connection methods.

Source: SKILL.md on GitHub

2 warnings8d5 checks · Risk SAFE
  • Gen Agent Trust Hub8d

    The skill provides a wrapper for WordPress Playground, a developer tool for running WordPress in the browser or via a local CLI. It includes capabilities for executing PHP code, modifying files, and downloading external resources such as Blueprints and plugins. While these are standard features for the intended use case, the ingestion of remote content from arbitrary URLs presents a potential indirect prompt injection surface.

  • Socket8d

    No alerts

  • Snyk8d

    Risk: MEDIUM · 1 issue

  • Runlayer7mo

    4/4 files flagged

  • ZeroLeaks5mo

    1 finding · Score: 86/100

Signed by skilld at e9c58d5. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 2 days ago.

Activeupdated last week
Other metadata
compatibility
Targets WordPress 7.0+, PHP 7.4.0+. Playground CLI requires Node.js 20.18+; runs WordPress in WebAssembly with SQLite.
  • CLI
  • wordpress
  • playground
  • webassembly
  • blueprints
  • php
  • plugin-testing
  • xdebug
  • sqlite

README badge

README badge for wordpress/agent-skills/wp-playground

Spins up disposable WordPress instances locally via Node.js CLI or in the browser, auto-mounting plugins and themes, with support for version switching, blueprints, and Xdebug debugging. Runs WordPress in WebAssembly with SQLite, targeting WordPress 6.9+ and PHP 7.2.24+.

Generated from the current SKILL.md.

Does this work with WordPress versions before 6.9?
No. This skill targets WordPress 6.9 and later, with PHP 7.2.24+.
What Node.js version is required?
Node.js 20.18 or higher is required to run the Playground CLI.
Can I use WordPress Playground with production data?
No. Playground instances are ephemeral and SQLite-backed; you should never point them at production data.
Does this skill support Xdebug debugging?
Yes. You can enable Xdebug with the `--xdebug` flag and connect your IDE (VS Code, PhpStorm) to debug plugin and theme code.
Can I run WordPress Playground entirely in the browser without CLI?
Yes. You can use playground.wordpress.net with blueprint URL fragments or query parameters, or the live Blueprint Editor to author and test without installing the CLI.

Generated from the current SKILL.md. These answers refresh after source changes.