Testing Wp Runtime Agent Skill
Guidelines for running wp-now to validate WordPress plugins and themes at runtime
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/Automattic/studio --skill testing-wp-runtimeThe instruction itself
7 sections, as written by the authorWhen to use me
Use this skill when you need to verify that a WordPress plugin or theme loads correctly at runtime.
Do not use this skill for static linting — use testing-php or testing-js for that.
Step 1: Determine the project mode
wp-now requires a --mode flag based on the project type:
- Plugin project (main PHP file has a
Plugin Name:header): use--mode=plugin - Theme project (contains
style.csswithTheme Name:header): use--mode=theme
Check the project root to determine which mode to use:
head -20 *.php style.css 2>/dev/null
Step 2: Start wp-now
Start wp-now in the background on an available port:
wp-now start --mode=<plugin|theme> --port=8881 &
Wait a few seconds for the server to initialize, then verify it is running:
curl -s -o /dev/null -w "%{http_code}" http://localhost:8881/
- HTTP 200 or 302 = server is running and WordPress loaded successfully.
- HTTP 500 = a fatal PHP error occurred — check debug log.
- Connection refused = server failed to start.
Step 3: Check for PHP errors
After the server starts, check the WordPress debug log for errors:
find /tmp -name "debug.log" -path "*/wp-content/*" 2>/dev/null | head -1 | xargs tail -50 2>/dev/null
Look for:
- Fatal errors: Plugin or theme could not load — must be fixed.
- Warnings/Notices: Non-fatal but should be reported.
- Deprecation notices: Report but do not fix.
Step 4: Validate HTTP responses
Test key endpoints to verify the project works:
# Homepage
curl -s -o /dev/null -w "%{http_code}" http://localhost:8881/
# wp-admin (should redirect to login)
curl -s -o /dev/null -w "%{http_code}" http://localhost:8881/wp-admin/
For plugins, also check if the plugin is active:
curl -s http://localhost:8881/ | grep -c "<plugin-specific-identifier>"
Step 5: Clean up
Always stop wp-now when done testing:
kill $(lsof -t -i:8881) 2>/dev/null
Rules
- Always clean up: Never leave wp-now running after testing is complete.
- Port 8881: Always use port 8881 to avoid conflicts.
- Timeout: If wp-now does not respond within 15 seconds of starting, consider it failed and kill the process.
- Never modify business logic: Only report issues found during runtime validation. Do not change how the code works.
- Report format: After testing, report results as:
- PASS: Server started, HTTP 200, no fatal errors in debug log
- FAIL: List specific errors (HTTP status, debug log entries, failed endpoints)
Other skills for the same job
different authors, same section of the catalogue
Rigorous visual validation expert specializing in UI testing, design system compliance, and accessibility verification. Masters screenshot analysis, visual regression testing, and component validation. Use PROACTIVELY to verify UI modifications have achieved their intended goals through comprehensive visual analysis.
Implement accessible user interfaces with semantic HTML, keyboard navigation, sufficient color contrast, screen reader support, ARIA attributes, and proper focus management. Use this skill when creating or editing React components (.tsx, .jsx files), when implementing forms with labels and inputs, when building interactive elements (buttons, modals, menus, dialogs), when implementing keyboard navigation, when choosing colors and ensuring contrast ratios, when adding ARIA attributes, when testing with screen readers, when implementing focus states and focus management, or when creating heading structures and page landmarks.
Build mobile-first responsive layouts with fluid containers, relative units, standard breakpoints, and touch-friendly design that adapts seamlessly across devices. Use this skill when creating or modifying layouts, implementing media queries, defining breakpoints, choosing sizing units, optimizing for mobile devices, or testing UI across screen sizes. Apply when working with responsive design, mobile layouts, tablet views, desktop views, viewport configuration, or any styling that needs to adapt to different screen sizes and device capabilities.
MUST USE after building/changing any UI or when asked whether a page, component, or TUI looks right. Rigorous visual QA across web/page and terminal UIs. Prefer browser:control-in-app-browser for unauthenticated browser/page QA in Codex, then Playwright/agent-browser/dev-browser. Captures screenshot/TUI evidence with bundled diff scripts, runs design-system/functional and visual-fidelity/CJK reviewer passes, then synthesizes a good/bad verdict. Triggers: visual QA, screenshot/pixel diff, UI looks wrong, reference fidelity, design system check, responsive check, CJK text clipping, TUI alignment, box-drawing drift.
Adds interactive widget previews to the project using the previews.dart system. Use when creating new UI components or updating existing screens to ensure consistent design and interactive testing.
Use when you need a deterministic inspection of a WordPress repository (plugin/theme/block theme/WP core/Gutenberg/full site) including tooling/tests/version hints, and a structured JSON report to guide workflows and guardrails.
29 production-ready scripts for iOS app testing, building, and automation. Provides semantic UI navigation, build automation, accessibility testing, and simulator lifecycle management. Optimized for AI agents with minimal token output.
Build and audit SwiftUI, UIKit, and AppKit accessibility for VoiceOver, Voice Control, Switch Control, Full Keyboard Access, Dynamic Type, focus restoration, labels/traits/actions, traversal, custom rotors, NSAccessibility, XCTest checks, adaptive system preferences, and App Store accessibility declarations. Use when implementing accessible UI, fixing an accessibility audit, testing assistive-technology behavior, or substantiating App Store Accessibility Nutrition Labels.
How to use it
Take automattic/testing-wp-runtime from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.