Playground Website Debugging
WordPress/wordpress-playground
Debug the WordPress Playground website by running the dev server from source and interacting with it via Playwright MCP.
Guidance for writing and running tests in Simple History, including the Premium add-on.
Install Testing
$ npx skills add bonny/WordPress-Simple-History --skill testing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install bonny/WordPress-Simple-History testing --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/bonny/WordPress-Simple-History.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/testing .claude/skills/testing && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "testing" agent skill from https://github.com/bonny/WordPress-Simple-History/tree/main/.claude/skills/testing into .claude/skills/testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/bonny/WordPress-Simple-History/tree/main/.claude/skills/testingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add bonny/WordPress-Simple-History --skill testing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install bonny/WordPress-Simple-History testing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bonny/WordPress-Simple-History.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/testing .agents/skills/testing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "testing" agent skill from https://github.com/bonny/WordPress-Simple-History/tree/main/.claude/skills/testing into .agents/skills/testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add bonny/WordPress-Simple-History --skill testing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install bonny/WordPress-Simple-History testing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bonny/WordPress-Simple-History.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/testing .cursor/skills/testing && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "testing" agent skill from https://github.com/bonny/WordPress-Simple-History/tree/main/.claude/skills/testing into .cursor/skills/testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/bonny/WordPress-Simple-History.git --path .claude/skills/testing--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add bonny/WordPress-Simple-History --skill testing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install bonny/WordPress-Simple-History testing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bonny/WordPress-Simple-History.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/testing .gemini/skills/testing && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "testing" agent skill from https://github.com/bonny/WordPress-Simple-History/tree/main/.claude/skills/testing into .gemini/skills/testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install bonny/WordPress-Simple-History testingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add bonny/WordPress-Simple-History --skill testing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/bonny/WordPress-Simple-History.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/testing .github/skills/testing && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "testing" agent skill from https://github.com/bonny/WordPress-Simple-History/tree/main/.claude/skills/testing into .github/skills/testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add bonny/WordPress-Simple-History --skill testing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install bonny/WordPress-Simple-History testing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bonny/WordPress-Simple-History.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/testing .opencode/skills/testing && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "testing" agent skill from https://github.com/bonny/WordPress-Simple-History/tree/main/.claude/skills/testing into .opencode/skills/testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
testing- GitHub stars
- 317
- Token cost
- ~5k tokens
- SKILL.md length
- 1,990 words
- Files
- 1
- Skills in repo
- 21
- Repo updated
- First seen
- Licence
- None found
At a glance
Guidance for writing and running tests in Simple History, including the Premium add-on.
- Tasks that involve Project scaffolding
- SKILL.md covers Which framework to use, Running tests, Testing Simple History Premium and Playwright setup, plus 2 more sections
- Calls npm, npx and docker; needs WP_ADMIN_PASSWORD
What it does
Testing is an agent skill from bonny/WordPress-Simple-History. Guidance for writing and running tests in Simple History, including the Premium add-on. Covers which framework to use, how to run existing tests, how to create new ones (codegen recording workflow), and how to test Premium (whose PHP tests live in this repo, not the add-ons repo).
Its SKILL.md is about 5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Testing & QA, covering Project scaffolding. It works with PHP, Playwright, WordPress and npm. The repository describes itself as: 🔍🕵️♀️ WordPress audit log that track user changes in WordPress admin using a nice activity feed.
When your agent uses it
- Tasks that involve Project scaffolding
Example prompts
- “/testing”
Requirements
- Node.js
- Docker
- Pre-approved tools (allowed-tools): Read, Bash, Edit, Write
What it can do on your machine
Read from SKILL.md and the folder at commit 24f337f. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadBashEditWrite
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
npmnpxdockergit
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
playwright.dev
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
WP_ADMIN_PASSWORD
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Testing loads about 5k tokens when it runs. Until then it costs about 72 tokens; SKILL.md has 1,990 words of instructions outside code blocks.
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
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NoteMentions a .env fileSKILL.md:280
- **Environment:** `.env.testing` in the repo root (params for the suite ymls) - NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
allowed-tools: Read, Bash, Edit, Write
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
Without a licence we can't republish the file, so here is its outline and opening line. It has 1,990 words (~4,974 tokens).
“Rule of thumb: If a human would test it by clicking around in a browser, use Playwright. If it's PHP logic, use Codeception.”
- name
- testing
- allowed-tools
- Read, Bash, Edit, Write
Files
Just SKILL.md in .claude/skills/testing of bonny/WordPress-Simple-History.
Open the folder on GitHubat commit 24f337f
Compare with similar skills
Testing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Testing this skillbonny/WordPress-Simple-History | 317 | — | ~5k | Automated safety check: Notes | None | |
| Playground Website DebuggingWordPress/wordpress-playground | 2k | — | ~1.9k | Automated safety check: Pass | GPL-2.0 | |
| DevAutomattic/wordpress-activitypub | 582 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Wordpress Sage Themegiuseppe-trisciuoglio/developer-kit | 355 | — | ~3.2k | Automated safety check: Notes | MIT | |
| Desktopgridaco/grida | 2.7k | — | ~3.2k | Automated safety check: Notes | Apache-2.0 | |
| Testingtrieb-work/nextjs-turbo-redis-cache | 151 | — | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
Dev
Automattic/wordpress-activitypub
Development workflows for WordPress ActivityPub plugin including wp-env setup, testing commands, linting, and build processes.
Wordpress Sage Theme
giuseppe-trisciuoglio/developer-kit
Provides WordPress theme development patterns using Sage (roots/sage) framework.
Desktop
gridaco/grida
Grida Desktop Electron shell and release-impact work: BrowserWindow, preload, window.grida, menus, protocol/deep links, file associations, Forge, path-scoped bridge security, Electron-only UI bugs…
Testing
trieb-work/nextjs-turbo-redis-cache
Run tests and add Next.js version coverage for the cache handler.
Run One Spec
LiberatedPixelCup/Universal-LPC-Spritesheet-Character-Generator
Run a single Node, browser, or Playwright spec instead of the full suite.
More from bonny/WordPress-Simple-History
All 21 skills in this repoBlueprint
bonny/WordPress-Simple-History
A skill your agent uses when the deliverable is WordPress Playground Blueprint JSON or a Blueprint bundle, including creating, editing, reviewing, validating schema keys, choosing steps/resources…
Action Links
bonny/WordPress-Simple-History
Guides implementation of structured action links on log events.
Changelog
bonny/WordPress-Simple-History
Adds changelog entries to readme.txt following keepachangelog format.
Code Quality
bonny/WordPress-Simple-History
Runs linting and static analysis on PHP/CSS/JS using phpcs, phpstan, and rector.
Create Logger
bonny/WordPress-Simple-History
Guides creation of custom loggers for Simple History. An agent skill from bonny/WordPress-Simple-History.
Logger Messages
bonny/WordPress-Simple-History
Enforces active voice for logger messages and the Event Details API.
Related
Works with
Categories
Questions about Testing
What does Testing do?
Guidance for writing and running tests in Simple History, including the Premium add-on. Testing is an agent skill from bonny/WordPress-Simple-History. Guidance for writing and running tests in Simple History, including the Premium add-on.
When should I use Testing?
Testing fits situations like: tasks that involve Project scaffolding.
How do I install Testing in Claude Code?
Run `npx skills add bonny/WordPress-Simple-History --skill testing -a claude-code`. Or copy the skill folder (.claude/skills/testing in bonny/WordPress-Simple-History) into .claude/skills/testing in your project. Claude Code loads it when a task matches its description.
How do I install Testing in Codex?
Run `npx skills add bonny/WordPress-Simple-History --skill testing -a codex`. Or copy the skill folder (.claude/skills/testing in bonny/WordPress-Simple-History) into .agents/skills/testing in your project. Codex loads it when a task matches its description.
Can I use Testing in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add bonny/WordPress-Simple-History --skill testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/testing, .gemini/skills/testing, .github/skills/testing and .opencode/skills/testing in your project.
What does Testing need to run?
Going by SKILL.md and its folder, Testing needs the command-line tools its instructions call (npm, npx, docker and git) and credentials named WP_ADMIN_PASSWORD. Our summary lists: Node.js; Docker. Its frontmatter pre-approves these tools: Read, Bash, Edit, Write.
Does Testing access the network?
SKILL.md names 1 domain. As links in the text: playwright.dev. This is read from the text; nothing was executed.
Is Testing safe to install?
Our automated static check of SKILL.md found notes only (mentions a .env file; pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Testing use?
No licence was found for Testing or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Testing use?
About 5k tokens (SKILL.md is roughly 20k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Testing?
Skills that share tags, products or a category with Testing: Playground Website Debugging (WordPress/wordpress-playground, 2k stars), Dev (Automattic/wordpress-activitypub, 582 stars), Wordpress Sage Theme (giuseppe-trisciuoglio/developer-kit, 355 stars) and Desktop (gridaco/grida, 2.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Testing?
bonny (a GitHub user) maintains it in bonny/WordPress-Simple-History, which has 317 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 7, 2026.
Source: bonny/WordPress-Simple-History on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.