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. Do NOT use for quick page debugging or network inspection (use chrome-devtools instead).
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionplaywright-skillExecute the skills CLI command in your project's root directory to begin installation:
Fetches playwright-skill from tech-leads-club/agent-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate playwright-skill. Access via /playwright-skill in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
4.4K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
4.4K
stars
| name | playwright-skill |
| description | 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. Do NOT use for quick page debugging or network inspection (use chrome-devtools instead). |
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)))"
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
/tmp/playwright-test-*.js (won't clutter your project)cd $SKILL_DIR && node run.js /tmp/playwright-test-*.jscd $SKILL_DIR
npm run setup
This installs Playwright and Chromium browser. Only needed once.
Step 1: Detect dev servers (for localhost testing)
cd $SKILL_DIR && node -e "require('./lib/helpers').detectDevServers().then(s => console.log(JSON.stringify(s)))"
Step 2: Write test script to /tmp with URL parameter
// /tmp/playwright-test-page.js
const { chromium } = require('playwright')
// Parameterized URL (detected or user-provided)
const TARGET_URL = 'http://localhost:3001' // <-- Auto-detected or from user
;(async () => {
const browser = await chromium.launch({ headless: false })
const page = await browser.newPage()
await page.goto(TARGET_URL)
console.log('Page loaded:', await page.title())
await page.screenshot({ path: '/tmp/screenshot.png', fullPage: true })
console.log('📸 Screenshot saved to /tmp/screenshot.png')
await browser.close()
})()
Step 3: Execute from skill directory
cd $SKILL_DIR && node run.js /tmp/playwright-test-page.js
// /tmp/playwright-test-responsive.js
const { chromium } = require('playwright')
const TARGET_URL = 'http://localhost:3001' // Auto-detected
;(async () => {
const browser = await chromium.launch({ headless: false, slowMo: 100 })
const page = await browser.newPage()
// Desktop test
await page.setViewportSize({ width: 1920, height: 1080 })
await page.goto(TARGET_URL)
console.log('Desktop - Title:', await page.title())
await page.screenshot({ path: '/tmp/desktop.png', fullPage: true })
// Mobile test
await page.setViewportSize({ width: 375, height: 667 })
await page.screenshot({ path: '/tmp/mobile.png', fullPage: true })
await browser.close()
})()
// /tmp/playwright-test-login.js
const { chromium } = require('playwright')
const TARGET_URL = 'http://localhost:3001' // Auto-detected
// SECURITY: Use environment variables for credentials
const TEST_EMAIL = process.env.TEST_EMAIL || '[email protected]'
const TEST_PASSWORD = process.env.TEST_PASSWORD || 'test-password'
;(async () => {
const browser = await chromium.launch({ headless: false })
const page = await browser.newPage()
await page.goto(`${TARGET_URL}/login`)
await page.fill('input[name="email"]', TEST_EMAIL)
await page.fill('input[name="password"]', TEST_PASSWORD)
await page.click('button[type="submit"]')
// Wait for redirect
await page.waitForURL('**/dashboard')
console.log('✅ Login successful, redirected to dashboard')
await browser.close()
})()
Execute with credentials:
[email protected] TEST_PASSWORD=secure123 \
cd $SKILL_DIR && node run.js /tmp/playwright-test-login.js
// /tmp/playwright-test-form.js
const { chromium } = require('playwright')
const TARGET_URL = 'http://localhost:3001' // Auto-detected
;(async () => {
const browser = await chromium.launch({ headless: false, slowMo: 50 })
const page = await browser.newPage()
await page.goto(`${TARGET_URL}/contact`)
await page.fill('input[name="name"]', 'John Doe')
await page.fill('input[name="email"]', '[email protected]')
await page.fill('textarea[name="message"]', 'Test message')
await page.click('button[type="submit"]')
// Verify submission
await page.waitForSelector('.success-message')
console.log('✅ Form submitted successfully')
await browser.close()
})()
const { chromium } = require('playwright')
;(async () => {
const browser = await chromium.launch({ headless: false })
const page = await browser.newPage()
await page.goto('http://localhost:3000')
const links = await page.locator('a[href^="http"]').all()
const results = { working: 0, broken: [] }
for (const link of links) {
const href = await link.getAttribute('href')
try {
const response = await page.request.head(href)
if (response.ok()) {
results.working++
} else {
results.broken.push({ url: href, status: response.status() })
}
} catch (e) {
results.broken.push({ url: href, error: e.message })
}
}
console.log(`✅ Working links: ${results.working}`)
console.log(`❌ Broken links:`, results.broken)
await browser.close()
})()
const { chromium } = require('playwright')
;(async () => {
const browser = await chromium.launch({ headless: false })
const page = await browser.newPage()
try {
await page.goto('http://localhost:3000', {
waitUntil: 'networkidle',
timeout: 10000,
})
await page.screenshot({
path: '/tmp/screenshot.png',
fullPage: true,
})
console.log('📸 Screenshot saved to /tmp/screenshot.png')
} catch (error) {
console.error('❌ Error:', error.message)
} finally {
await browser.close()
}
})()
// /tmp/playwright-test-responsive-full.js
const { chromium } = require('playwright')
const TARGET_URL = 'http://localhost:3001' // Auto-detected
;(async () => {
const browser = await chromium.launch({ headless: false })
const page = await browser.newPage()
const viewports = [
{ name: 'Desktop', width: 1920, height: 1080 },
{ name: 'Tablet', width: 768, height: 1024 },
{ name: 'Mobile', width: 375, height: 667 },
]
for (const viewport of viewports) {
console.log(`Testing ${viewport.name} (${viewport.width}x${viewport.height})`)
await page.setViewportSize({
width: viewport.width,
height: viewport.height,
})
await page.goto(TARGET_URL)
await page.waitForTimeout(1000)
await page.screenshot({
path: `/tmp/${viewport.name.toLowerCase()}.png`,
fullPage: true,
})
}
console.log('✅ All viewports tested')
await browser.close()
})()
For quick one-off tasks, you can execute code inline without creating files:
# Take a quick screenshot
cd $SKILL_DIR && node run.js "
const browser = await chromium.launch({ headless: false });
const page = await browser.newPage();
await page.goto('http://localhost:3001');
await page.screenshot({ path: '/tmp/quick-screenshot.png', fullPage: true });
console.log('Screenshot saved');
await browser.close();
"
When to use inline vs files:
Optional utility functions in lib/helpers.js:
const helpers = require('./lib/helpers')
// Detect running dev servers (CRITICAL - use this first!)
const servers = await helpers.detectDevServers()
console.log('Found servers:', servers)
// Safe click with retry
await helpers.safeClick(page, 'button.submit', { retries: 3 })
// Safe type with clear
await helpers.safeType(page, '#username', 'testuser')
// Take timestamped screenshot
await helpers.takeScreenshot(page, 'test-result')
// Handle cookie banners
await helpers.handleCookieBanner(page)
// Extract table data
const data = await helpers.extractTableData(page, 'table.results')
See lib/helpers.js for full list.
Configure custom headers for all HTTP requests via environment variables. Useful for:
Single header (common case):
PW_HEADER_NAME=X-Automated-By PW_HEADER_VALUE=playwright-skill \
cd $SKILL_DIR && node run.js /tmp/my-script.js
Multiple headers (JSON format):
PW_EXTRA_HEADERS='{"X-Automated-By":"playwright-skill","X-Debug":"true"}' \
cd $SKILL_DIR && node run.js /tmp/my-script.js
Headers are automatically applied when using helpers.createContext():
const context = await helpers.createContext(browser)
const page = await context.newPage()
// All requests from this page include your custom headers
For scripts using raw Playwright API, use the injected getContextOptionsWithHeaders():
const context = await browser.newContext(getContextOptionsWithHeaders({ viewport: { width: 1920, height: 1080 } }))
For comprehensive Playwright API documentation, see API_REFERENCE.md:
detectDevServers() before writing test code for localhost testingPW_HEADER_NAME/PW_HEADER_VALUE env vars to identify automated traffic to your backend/tmp/playwright-test-*.js, never to skill directory or user's projectTARGET_URL constant at the top of every scriptheadless: false unless user explicitly asks for headless modeheadless: true when user specifically requests "headless" or "background" executionslowMo: 100 to make actions visible and easier to followwaitForURL, waitForSelector, waitForLoadState instead of fixed timeoutsconsole.log() to track progress and show what's happeningPlaywright not installed:
cd $SKILL_DIR && npm run setup
Module not found:
Ensure running from skill directory via run.js wrapper
Browser doesn't open:
Check headless: false and ensure display available
Element not found:
Add wait: await page.waitForSelector('.element', { timeout: 10000 })
User: "Test if the marketing page looks good"
Claude: I'll test the marketing page across multiple viewports. Let me first detect running servers...
[Runs: detectDevServers()]
[Output: Found server on port 3001]
I found your dev server running on http://localhost:3001
[Writes custom automation script to /tmp/playwright-test-marketing.js with URL parameterized]
[Runs: cd $SKILL_DIR && node run.js /tmp/playwright-test-marketing.js]
[Shows results with screenshots from /tmp/]
User: "Check if login redirects correctly"
Claude: I'll test the login flow. First, let me check for running servers...
[Runs: detectDevServers()]
[Output: Found servers on ports 3000 and 3001]
I found 2 dev servers. Which one should I test?
- http://localhost:3000
- http://localhost:3001
User: "Use 3001"
[Writes login automation to /tmp/playwright-test-login.js]
[Runs: cd $SKILL_DIR && node run.js /tmp/playwright-test-login.js]
[Reports: ✅ Login successful, redirected to /dashboard]
/tmp for automatic cleanup (no clutter)run.jsPrerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
tech-leads-club/agent-skills
tech-leads-club/agent-skills
tech-leads-club/agent-skills
supercent-io/skills-template
kunchenguid/no-mistakes
BuilderIO/skills
I recommend playwright-skill for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Solid pick for teams standardizing on skills: playwright-skill is focused, and the summary matches what you get after install.
Useful defaults in playwright-skill — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
playwright-skill reduced setup friction for our internal harness; good balance of opinion and flexibility.
I recommend playwright-skill for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
playwright-skill reduced setup friction for our internal harness; good balance of opinion and flexibility.
Keeps context tight: playwright-skill is the kind of skill you can hand to a new teammate without a long onboarding doc.
We added playwright-skill from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Registry listing for playwright-skill matched our evaluation — installs cleanly and behaves as described in the markdown.
playwright-skill fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 63