WP Admin Browser
Drives real WordPress admin actions via Chrome DevTools MCP with safety rails.
Test report
- Verdict
- Works with setup
- Score
- Tested
- Jul 14, 2026
- Environment
- Claude Code 2.x (agent harness)
- Upstream re-checked
- Aug 10, 2026 · 4e15797
Its 'never touch the main admin, always spin up then delete a temp admin' rule and menu-only navigation checklist close real gaps in agentic WP-admin automation, but the skill is unusable without Chrome DevTools MCP wired up plus a live WordPress admin — this sandbox had neither (no Docker for a real install; WordPress Playground's in-browser WASM boot stalled at ~65% for 30+ seconds and never finished), so Stage 3 is a documented process comparison, not a live run.
Scored on four weighted criteria — install, triggering, output vs. baseline, docs. How scoring works
- Installs cleanly 5/5
- Triggers reliably 5/5
- Output vs. baseline 6/10
- Docs & honesty 4/5
What WP Admin Browser does
Automates WordPress admin panel interaction through Chrome DevTools MCP — logging in, navigating menus, filling forms, and creating a disposable temp-admin account instead of touching the real one. Triggers on phrasing like 'log in to WP admin', 'fill in this form in the browser', or 'take a screenshot of the admin page'. Requires an active Chrome DevTools MCP connection and a reachable WordPress instance to actually execute.
How to install WP Admin Browser
git clone https://github.com/mralaminahamed/wp-dev-skills
cd wp-dev-skills
mkdir -p ~/.claude/skills
cp -r skills/wp-admin-browser ~/.claude/skills/wp-admin-browser
Skills live in ~/.claude/skills/ (global) or .claude/skills/
(per-project). Restart Claude Code after installing.
Commands — how to trigger WP Admin Browser
-
/wp-admin-browserDrives real WordPress admin actions via Chrome DevTools MCP with safety rails.
It also activates on plain-language prompts like these:
-
Create a temporary admin user in WordPress and clean it up after -
Log into my WordPress admin and update the site tagline -
Verify a new WP admin account then delete it when done
Frequently asked questions
- Is the WP Admin Browser skill free?
- Yes. The skill itself is free from mralaminahamed/wp-dev-skills. SkillProof publishes the install command and an independent test verdict at no cost.
- Does WP Admin Browser work with Claude Code?
- We tested it with Claude Code 2.x (agent harness) on Jul 14, 2026. Verdict: Works with setup. Its 'never touch the main admin, always spin up then delete a temp admin' rule and menu-only navigation checklist close real gaps in agentic WP-admin automation, but the skill is unusable without Chrome DevTools MCP wired up plus a live WordPress admin — this sandbox had neither (no Docker for a real install; WordPress Playground's in-browser WASM boot stalled at ~65% for 30+ seconds and never finished), so Stage 3 is a documented process comparison, not a live run.
- What is the WP Admin Browser SkillProof Score?
- 8.0/10 — installs cleanly 5/5, triggers reliably 5/5, output vs. baseline 6/10, docs & honesty 4/5.
- How do I install WP Admin Browser?
- Copy the install command from this page, run it in your terminal, and restart Claude Code. Skills live in ~/.claude/skills/ (global) or .claude/skills/ inside a project.
- Can I use WP Admin Browser with Cursor, Copilot, Gemini CLI, Codex or other AI tools?
- The SKILL.md format is native to Claude (Claude Code, Desktop, claude.ai). The instructions inside adapt to other assistants: Cursor rules, GitHub Copilot instructions, Windsurf rules, Custom GPTs, AGENTS.md for OpenAI Codex, and GEMINI.md for Google Gemini CLI — our conversion guides cover each, and the free converter on the tools page does the wrapping for you.