SkillsAdd

wordpress/agent-skills · Official

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, snapshots, mounts, version switching, and Xdebug.

All-time #3858 Trending #3772 First seen Feb 1, 2026
8-week activity · all time api

Installation

$ npx skills add wordpress/agent-skills --skill wp-playground
View on skills.sh ↗ GitHub repository ↗

Summary

  • 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, snapshots, mounts, version switching, and Xdebug.
  • For Blueprint JSON authoring or review, use the blueprint skill directly.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

agent-browser Shared topics
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
azure-aigateway Shared topics
microsoft/azure-skills

Configure Azure API Management as an AI Gateway for AI models, MCP tools, and agents. WHEN: sem…

566.3K installs
azure-compute Shared topics
microsoft/azure-skills

Azure VM/VMSS router. WHEN: create / provision / deploy / spin-up VM, recommend VM size, compar…

510K installs
supabase-postgres-best-practices Shared topics
supabase/agent-skills

Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill …

391.6K installs
prisma-cli Shared topics
prisma/skills

Prisma ORM CLI commands reference covering init, generate, migrate, db, dev, complete, studio, …

267K installs
supabase Shared topics
supabase/agent-skills

Use when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge F…

263K installs

Also in this package

Other skills from wordpress/agent-skills · top by installs.

npx skills add wordpress/agent-skills
wp-plugin-development 6.1K wp-rest-api 4.5K wp-block-themes 4.5K wp-performance 4.5K wp-block-development 4.2K wordpress-router 4.2K wp-wpcli-and-ops 4K wp-project-triage 3.9K wp-phpstan 3.4K wp-abilities-api 3.3K

Browse all from wordpress/agent-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 2.1K
License LICENSE
Default branch trunk
Open issues 25
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

CompatibilityTargets WordPress 7.0+, PHP 7.4.0+. Playground CLI requires Node.js 20.18+; runs WordPress in WebAssembly with SQLite.

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,701 B
  • docs SUMMARY.md 319 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 3,500 installs

SKILL.md

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 playground.wordpress.net, share URLs, Blueprint Editor, hosted bundles, and browser limitations.

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.