Wp Playground Development

What it does

When your agent uses it

• Reviewing Blueprints
• Playground JSON setup flows
• @wp-playground/cli usage
• Embedded Playground demos

Example prompts

• “WordPress Playground”
• “Blueprint”
• “playground.json”
• “/wp-playground-development”

Requirements

• Node.js

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

1. 1Identify the Playground entrypoint
2. 2Check reproducibility first
3. 3Review setup steps
4. 4Review developer ergonomics
5. 5Classify findings

What it can do on your machine

Read from SKILL.md and the folder at commit 8c96442. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  Shell commands in SKILL.md call:

  • rg
  • npx

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Wp Playground Development loads about 1.2k tokens when it runs, and up to ~3k if it reads all its reference files. Until then it costs about 127 tokens; SKILL.md has 487 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~127

When it runs · the whole SKILL.md, loaded when a task matches

~1.2k

With references · SKILL.md plus every file in references/, read only if the agent opens them

~3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jorgerosal/wordpress-skills at commit 8c96442, republished under its MIT licence (© jorgerosal). 487 words, ~1,230 tokens.

name

wp-playground-development

description

WordPress Playground review and development guidance. Use when reviewing Blueprints, Playground JSON setup flows, `@wp-playground/cli` usage, embedded Playground demos, reproducible bug repros, docs examples, or when user mentions "WordPress Playground", "Blueprint", "playground.json", "run-blueprint", "build-snapshot", "embed Playground", or "zero-setup repro". Helps review Blueprint design, local Playground workflows, demo reliability, and reproducible WordPress environments.

rg -n "playground|blueprint|@wp-playground" . -g '*.{md,json,js,ts,tsx,yml,yaml}'
rg -n "\"steps\"|\"landingPage\"|\"preferredVersions\"" . -g '*.json'

rg -n "run-blueprint|build-snapshot|@wp-playground/cli|npx @wp-playground/cli" . -g '*.{md,js,ts,sh,yml,yaml}'
rg -n "blueprint-url|playground.wordpress.net|wordpress.org/playground" . -g '*.{md,html,js,ts}'

rg -n "\"step\": \"(login|wp-cli|installPlugin|installTheme|writeFile|mkdir|cp|mv|enableMultisite)\"" . -g '*.json'

© jorgerosal, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files (references) in claude-skills/wp-playground-development of jorgerosal/wordpress-skills.

• SKILL.md
• references/blueprint-patterns.md
• references/cli-and-local-workflows.md
• references/embedding-and-repros.md
• references/sample-playground-blueprint.json

Open the folder on GitHubat commit 8c96442