Guide for extending Playwright with new APIs, MCP tools, CLI commands, and vendored dependencies.
Works with
Covers monorepo structure, build/test/lint workflows, and coding conventions via CLAUDE.md reference
Includes detailed walkthroughs for implementing client/server APIs, writing tests, and modifying protocol layers
Explains how to add MCP tools, CLI commands, and configuration options within the Playwright ecosystem
Documents the vendoring process for bundling third-party npm packages
See CLAUDE.md for monorepo structure, build/test/lint commands, and coding conventions.
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionplaywright-devExecute the skills CLI command in your project's root directory to begin installation:
Fetches playwright-dev from microsoft/playwright 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-dev. Access via /playwright-dev 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
85.7K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
85.7K
stars
Prerequisites
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.
microsoft/playwright-cli
github/awesome-copilot
greekr4/playwright-bot-bypass
testdino-hq/playwright-skill
0xbigboss/claude-code
solana-foundation/solana-dev-skill
Useful defaults in playwright-dev — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
playwright-dev fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
I recommend playwright-dev for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Keeps context tight: playwright-dev is the kind of skill you can hand to a new teammate without a long onboarding doc.
playwright-dev is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
playwright-dev is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
playwright-dev has been reliable in day-to-day use. Documentation quality is above average for community skills.
Registry listing for playwright-dev matched our evaluation — installs cleanly and behaves as described in the markdown.
I recommend playwright-dev for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
playwright-dev fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 74