Playwriter
- 10 installs
- 356 repo stars
- Updated March 25, 2026
- brianlovin/agent-config
This is a copy of playwriter by brianlovin - installs and ranking accrue to the original listing.
playwriter is a Claude skill that controls the user's currently open Chrome tab via the Playwriter CLI to inspect live UI, run scripted actions, and reproduce frontend issues.
About
playwriter is a skill that controls the user's already-open Chrome tab through the Playwriter CLI instead of launching a new browser. Developers use it to inspect live UI state, run scripted browser actions, capture console output, and reproduce frontend issues directly in the user's tab. It attaches to a session and runs Playwright-style page commands against that tab.
- Drives the user's currently open Chrome tab via the Playwriter CLI, no new browser launch
- Inspects live UI state, runs scripted actions, and captures console output to reproduce frontend issues
- Uses page.evaluate and accessibility snapshots to read structured state from the active app
Playwriter by the numbers
- 10 all-time installs (skills.sh)
- Data as of Aug 1, 2026 (Skillselion catalog sync)
playwriter capabilities & compatibility
- Capabilities
- browser control · frontend debugging · console inspection · ui state inspection
- Works with
- chrome
- Use cases
- debugging · frontend
- Pricing
- Free
What playwriter says it does
Control the user's currently open Chrome tab through the Playwriter CLI (no new browser launch).
Use this skill to drive the user's active Chrome tab via Playwriter.
Prefer read-only inspection unless the task requires mutation.
npx skills add https://github.com/brianlovin/agent-config --skill playwriterAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 10 |
|---|---|
| repo stars | ★ 356 |
| Last updated | March 25, 2026 |
| Repository | brianlovin/agent-config ↗ |
What it does
Drive the user's open Chrome tab to inspect live UI, run scripted actions, and reproduce frontend issues in place.
Who is it for?
Inspecting live UI state and reproducing frontend bugs in the user's own Chrome tab
When should I use this skill?
You need to inspect live UI state, run scripted browser actions, capture console output, or reproduce a frontend issue in the current tab
What you get
Live UI state and console output inspected in place, with reproducible actions in the user's tab.
- Live UI state and console findings
- Reproduced frontend issues
Files
Playwriter
Use this skill to drive the user's active Chrome tab via Playwriter.
Full documentation is available here: https://playwriter.dev/
Quick Start
1. Ensure the Playwriter extension is enabled (green) on the target tab. 2. Ensure CLI is available:
playwriter --version || npx -y playwriter --version3. Create/attach a session:
playwriter session new4. Run commands against that session:
playwriter -s 1 -e "console.log(await page.url())"Core Workflow
1. Confirm connection and correct tab:
playwriter -s <session> -e "console.log(await page.url()); console.log(await page.title());"2. Collect page structure when needed:
playwriter -s <session> -e "console.log(await accessibilitySnapshot({ page }))"3. Execute targeted actions (click/type/hover/fetch/evaluate). 4. Pull logs and structured state via page.evaluate. 5. Summarize findings with exact IDs, timestamps, and observed state transitions.
Useful Commands
Get list rows/options from current app UI:
playwriter -s <session> -e "const rows = await page.getByRole('option').all(); console.log(rows.length);"Read popup/hover content:
playwriter -s <session> -e "const row = page.getByRole('option').nth(0); await row.hover(); await page.waitForTimeout(700); console.log(await page.locator('[data-side]').first().innerText());"Run arbitrary in-page debug code:
playwriter -s <session> -e "const out = await page.evaluate(() => ({ href: location.href })); console.log(out);"Troubleshooting
- If the session attaches to the wrong tab, click the extension icon on the intended tab and re-run
playwriter session new. - If
playwritercommand is missing, usenpx -y playwriter ...or install globally. - If execution errors suggest stale connection, create a fresh session.
Guardrails
- Prefer read-only inspection unless the task requires mutation.
- Announce destructive UI actions before running them.
- When capturing logs, redact sensitive tokens/user data in summaries.
interface:
display_name: "Playwriter Browser Control"
short_description: "Use Playwriter CLI to control an open Chrome tab."
default_prompt: "Use Playwriter CLI to attach to the active browser tab, inspect state, run actions, and capture logs for debugging."
Related skills
Azure DiagnosticsSystematically diagnose and resolve production issues on Microsoft Azure using official Microsoft guidance.495k1.3kAzure MessagingQuickly diagnose and fix connection, authentication, and message-processing failures when using Azure Event Hubs or Service Bus SDKs.483k1.3k
Diagnosing BugsGet a systematic, step-by-step process that surfaces the real root cause instead of guessing at bugs.291k200k
Use My BrowserWhen their agent task requires access to the live browser session, rendered DOM state, authenticated dashboards, localhost apps, or DevTools-selected elements instea269k71
Systematic DebuggingFollow a repeatable four-phase process that forces root-cause discovery before any code changes.210k265k
Safe DebugGet conservative, non-destructive diagnosis of deep learning and agent errors before any code changes are made.185k512FAQ
Does it open a new browser?
No, it drives the user's currently open Chrome tab via the Playwriter extension and CLI.
How do I start a session?
Run `playwriter session new`, then run commands against it with `playwriter -s <session> -e ...`.
Is it read-only?
It prefers read-only inspection and announces destructive UI actions before running them.