Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to /tmp. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check links, automate any browser task.
NewMaintained
Automatic
◆QA & Test Engineering pack
Last verified 8/21/2026
What it changes
Passed 5 of 9 test cases with the skill, and 5 of 9 without it.
Without skill50%
With skill50%
Checks it passed that the model alone missed
Writes test script under /tmp.
Executes script using node run.js.
Executes code inline using node run.js with an inline JavaScript snippet string.
and 1 more in the full report
2 fixed5 passed either way15 still failing0 broke
Pass-rate lift
0 pp
Tokens
+117%
Agent turns
0%
Response time
-32%
Model gemini-3.6-flashMeasured 8/21/2026v27 of 22 cases passed with skill · 9 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 2
Prompt
I need a quick one-liner command to check if my local server on port 3001 returns a valid page title without saving any script files.
What was checked, without and with the skill
Checked
Without skill
With skill
Executes code inline using node run.js with an inline JavaScript snippet string.
Missed
Passed
case-10 · gemini-3.6-flash · 8/21/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md398 linessingle file
IMPORTANT - Path Resolution:
This skill can be installed in different locations (plugin system, manual installation, global, or project-specific). Before executing any commands, determine the skill directory based on where you loaded this SKILL.md file, and use that path in all commands below. Replace $SKILL_DIR with the actual discovered path.
General-purpose browser automation skill. I'll write custom Playwright code for any automation task you request and execute it via the universal executor.
CRITICAL WORKFLOW - Follow these steps in order:
Auto-detect dev servers - For localhost testing, ALWAYS run server detection FIRST:
cd $SKILL_DIR && node -e "require('./lib/helpers').detectDevServers().then(servers => console.log(JSON.stringify(servers)))"
If 1 server found: Use it automatically, inform user
If multiple servers found: Ask user which one to test
If no servers found: Ask for URL or offer to help start dev server
Write scripts to /tmp - NEVER write test files to skill directory; always use /tmp/playwright-test-*.js
Use visible browser by default - Always use headless: false unless user specifically requests headless mode
Parameterize URLs - Always make URLs configurable via environment variable or constant at top of script
How It Works
You describe what you want to test/automate
I auto-detect running dev servers (or ask for URL if testing external site)
I write custom Playwright code in /tmp/playwright-test-*.js (won't clutter your project)
I execute it via: cd $SKILL_DIR && node run.js /tmp/playwright-test-*.js
Results displayed in real-time, browser window visible for debugging
Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to /tmp. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check links, automate any browser task. Use when user wants to test websites, automate browser interactions, validate web functionality, or perform any browser-based testing.