use-playwright-cli
Browser automation and testing via Playwright.
Install
mkdir -p .claude/skills/use-playwright-cli && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/12684" && unzip -o skill.zip -d .claude/skills/use-playwright-cli && rm skill.zipInstalls to .claude/skills/use-playwright-cli
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use when the user wants to automate, inspect, debug, or verify browser behavior in this repo with Playwright CLI, or wants concise guidance on using Playwright CLI inside Codex.Key capabilities
- →Reproduce UI bugs in running apps
- →Click through flows to confirm behavior
- →Capture screenshots or visual proof
- →Check console, network, or navigation behavior
- →Explain Playwright CLI steps
- →Report exact failing steps or errors
How it works
The skill uses Playwright CLI to automate browser interactions based on user input, verifying UI behavior and capturing evidence.
Inputs & outputs
When to use use-playwright-cli
- →Verifying UI rendering
- →Reproducing browser bugs
- →Automating user flow tests
About this skill
Use Playwright CLI
Use this skill when a task needs browser-level verification instead of source-only inspection. Typical cases:
- Reproduce a UI bug in a running app
- Click through a flow and confirm it behaves as expected
- Capture a screenshot or visual proof
- Check console, network, or navigation behavior
- Explain how to ask Codex to run a Playwright CLI workflow
How to use it
- Start or confirm the app you want to test.
- Invoke this skill explicitly with
$use-playwright-cliwhen you want Codex to handle the browser flow. - Give the target URL, the user journey, and the expected result.
- Ask for concrete evidence when needed: screenshot, failing step, selector, or error text.
Good prompts
Use $use-playwright-cli to open localhost:5173 and verify the homepage renders.Use $use-playwright-cli to reproduce the modal bug and capture the failure.Use $use-playwright-cli to click through checkout and report any console errors.Use $use-playwright-cli to explain the Playwright CLI steps for this repo.
Execution rules
- Prefer stable selectors and visible text over brittle DOM paths.
- Wait for the UI to settle before asserting results.
- If the app is not running, start it first or ask for the dev server command.
- If source inspection is enough, read the files first instead of using browser automation.
- When a browser run fails, report the exact step, selector, or error that broke.
Output
When you use this skill, return a short, actionable result:
- what was tested
- the command or steps used
- the outcome
- any evidence or blocker
When not to use it
- →When source-only inspection is sufficient
- →When the app is not running
- →When not needing browser-level verification
Limitations
- →Requires the app to be running
- →Prefers stable selectors and visible text
- →Requires waiting for UI to settle before asserting results
How it compares
This skill provides direct browser automation and verification using Playwright CLI, offering concrete evidence of UI behavior, unlike manual testing or source code review.
Compared to similar skills
use-playwright-cli side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| use-playwright-cli (this skill) | 0 | 2mo | No flags | Intermediate |
| webapp-testing | 353 | 3mo | Review | Intermediate |
| ui-ux-expert-skill | 91 | 9mo | Review | Advanced |
| accessibility | 42 | 5mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
webapp-testing
anthropics
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
ui-ux-expert-skill
fercracix33
Technical workflow for implementing accessible React user interfaces with shadcn/ui, Tailwind CSS, and TanStack Query. Includes 6-phase process with mandatory Style Guide compliance, Context7 best practices consultation, Chrome DevTools validation, and WCAG 2.1 AA accessibility standards. Use after Test Agent, Implementer, and Supabase agents complete their work.
accessibility
tech-leads-club
Audit and improve web accessibility following WCAG 2.1 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible".
playwright-browser-automation
lackeyjb
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.
svelte-expert
Raudbjorn
Expert Svelte/SvelteKit development assistant for building components, utilities, and applications. Use when creating Svelte components, SvelteKit applications, implementing reactive patterns, handling state management, working with stores, transitions, animations, or any Svelte/SvelteKit development task. Includes comprehensive documentation access, code validation with svelte-autofixer, and playground link generation.
browser-daemon
noiv
Persistent browser automation via Playwright daemon. Keep a browser window open and send it commands (navigate, execute JS, inspect console). Perfect for interactive debugging, development, and testing web applications. Use when you need to interact with a browser repeatedly without opening/closing it.