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.

referenceswebmcp.md

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

WebMCP site tools

Use this reference when interacting with the open Playground page through callable WebMCP tools. For setup or connection-method selection, use website workflows.

Discover and call tools

  1. Use the intended Playground tab, wait for WordPress to load, and discover the site's tools through the browser environment's tool discovery mechanism (sometimes called Site tools).
  2. Inspect each discovered tool's description and input schema before calling it. Do not assume that Playground MCP and WebMCP expose identical interfaces.
  3. Confirm the target site with a harmless information/read operation, then use the discovered tool for the requested operation.

WebMCP exposes tools through the open webpage. It does not require the local Playground MCP server, its WebSocket bridge, or mcp=yes.

Examples to look for during discovery include:

Purpose Example WebMCP tools
Site information and persistence playground_get_site_info, playground_list_sites, playground_rename_site, playground_save_in_browser
PHP and WordPress requests playground_execute_php, playground_request
Navigation playground_navigate, playground_get_current_url
Filesystem operations playground_read_file, playground_write_file, playground_list_files, playground_mkdir

Use the discovered tool set as the source of truth. Playground can also proxy tools registered by plugins inside the WordPress iframe onto the outer page; rediscover tools after navigation or a site switch when needed. A WordPress ability registration alone does not make it a WebMCP tool.

Background: WordPress Playground and WebMCP: bringing AI agents into your browser workflow.

Unsupported operations

If WebMCP is unavailable or lacks an operation, return to the interaction router and read the selected fallback reference. Preserve the intended site when changing methods; do not create a replacement or reload away current work.

Verification

Check tool results and verify the requested state in the same site before claiming success. After navigation or a site switch, confirm the active site and rediscover tools when needed.

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.