SkillAgentSearch skills...

wp-playground

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.

Install / Use

npx skills add WordPress/agent-skills --skill wp-playground

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

81/100

Category

Automation

Supported Platforms

Universal

Our assessment of wp-playground

wp-playground scores 81/100 on our quality scale, 2381st of 2,790 Automation skills we index.

Its SKILL.md is 3.8 KB long, split into 7 sections and no code examples: a solid amount of guidance for an agent.

With 2,162 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
11/20
Description
15/15
Adoption
14/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so wp-playground is actively maintained.
  • Our last check on 2026-11-08 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-30. Automated pattern scan on 2026-09-30. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

wp-playground compared with similar skills

All 4 of these similar skills score higher than wp-playground; compare them before choosing.

SkillScoreStarsUpdatedFormat
wp-playground (this skill)by WordPress812.2k54d agoSKILL.md
claude-memby thedotmack100117.6ktodayCLAUDE.md
Agent-Reachby Panniantong100112.3k8d agoCLAUDE.md
rufloby ruvnet10081.9ktodayCLAUDE.md
headroomby headroomlabs-ai10079.8ktodayCLAUDE.md

Frequently asked questions

How do I install wp-playground?
Run npx skills add WordPress/agent-skills --skill wp-playground. The install tabs above show the steps for each supported agent.
Which AI agents does wp-playground work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is wp-playground safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is wp-playground still maintained?
The repository was last updated about 2 months ago, so wp-playground is actively maintained.

name: wp-playground description: "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." compatibility: "Targets WordPress 7.0+, PHP 7.4.0+. Playground CLI requires Node.js 20.18+; runs WordPress in WebAssembly with SQLite."

WordPress Playground

This is a thin routing wrapper. Use it to pick the right Playground workflow, then load only the focused reference or skill needed for the task.

Procedure

  1. Identify the user intent: Blueprint authoring/review, local CLI execution, browser-only website/share link workflow, Xdebug/stuck CLI run, or a mixed Playground request.
  2. Route to the focused source below, loading more than one only when the request has multiple distinct parts.
  3. For mixed requests, delegate Blueprint JSON work to blueprint, then return here for runtime, CLI, debugging, or sharing guidance.
  • Blueprint JSON, schema, steps, resources, bundles, or Blueprint review: use the blueprint skill directly. Do not duplicate Blueprint schema details here.
  • Local CLI execution: read references/cli.md for @wp-playground/cli server, run-blueprint, build-snapshot, mounts, version switching, and local validation.
  • Xdebug or stuck CLI runs: read references/debugging.md for Xdebug, runtime logs, worker flags, and stuck CLI runs.
  • Browser-only Playground website workflows: read references/website.md for Query API and Blueprint URL setup, share links, and browser limitations. It routes existing-site operations to separate WebMCP, Playground MCP, and Sites API references; load only the selected method. Unless the user requests a specific connection method, prefer available WebMCP tools for supported browser operations.

Inputs required

  • The intended workflow: Blueprint authoring, local CLI run, website/share link, snapshot, or debugging.
  • Project or bundle path if local code must be mounted or packaged.
  • Desired WordPress/PHP versions if compatibility matters.
  • Port preference if a local server is needed.
  • Whether browser-only sharing or local filesystem access is required.

Guardrails

  • Playground instances are disposable, SQLite-backed environments; never point them at production data.
  • Keep Blueprint JSON guidance in blueprint so the schema and examples have one source of truth.
  • For local CLI work, verify Node.js 20.18+ and npm/npx before running commands.
  • Browser-only Playground cannot read local filesystem paths; use public URLs, hosted ZIP bundles, or inline Blueprint JSON.

Verification

  • For Blueprint content, validate against the published schema and follow the blueprint skill verification.
  • For local CLI runs, verify the mounted plugin/theme or Blueprint side effects in the Playground instance.
  • For share links, open the generated URL and confirm the expected landing page and installed assets load.

Failure modes

  • Blueprint work routed here: stop and use the blueprint skill for schema keys, steps, resources, bundles, validation, or Blueprint review.
  • Local filesystem needed in a browser-only workflow: use references/cli.md; playground.wordpress.net cannot read local filesystem paths.
  • Shareable browser link requested from a local CLI workflow: use references/website.md; local server URLs are not portable share links.
  • Debugging treated as a second-hop reference: read references/debugging.md directly for Xdebug, logs, worker flags, and stuck CLI runs.

Escalation

  • If the task needs PHP extensions, native database access, persistence, or production-like infrastructure that Playground cannot provide, use a full WordPress stack such as wp-env, Docker, or the project-provided environment.

Related Skills

View on GitHub
GitHub Stars2.2k
CategoryAutomation
Updated1mo ago
Forks322

Languages

JavaScript

Trust signals

88/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium