Interactive browser automation with snapshot-based element references and multi-session support.
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
Time estimate: 15-45 minutes depending on use case complexity
Prerequisites
Submit your Claude Code skill and start earning
epx add microsoft/playwright --skill playwright-cliCompatible with
Supported agents
40+ commands across navigation, interaction, keyboard/mouse control, storage management, network mocking, and DevTools integration
Automatic page snapshots after each command with element references (e.g., e15 ) for reliable, context-aware interactions
Multi-browser support (Chrome, Firefox, WebKit, Edge) with persistent profiles, session management, and named browser instances
Built-i
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionplaywright-cliExecute the skills CLI command in your project's root directory to begin installation:
epx add microsoft/playwright --skill playwright-cliFetches playwright-cli 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:
.cursor/skills/playwright-cli
Restart Cursor to activate playwright-cli. Access via /playwright-cliin your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
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.
playwright-mcp-dev
microsoft/playwright · Testing · same repo
playwright-cli
microsoft/playwright-cli · Testing · 2 shared tags
playwright-skill
testdino-hq/playwright-skill · Testing · tag: playwright
playwright-generate-test
github/awesome-copilot · Testing · tag: playwright
symfony:e2e-panther-playwright
makfly/superpowers-symfony · Testing · tag: playwright
feishu-cli-perm
riba2534/feishu-cli · Productivity · tag: cli
playwright-cli is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: playwright-cli is the kind of skill you can hand to a new teammate without a long onboarding doc.
I recommend playwright-cli for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Keeps context tight: playwright-cli is the kind of skill you can hand to a new teammate without a long onboarding doc.
Useful defaults in playwright-cli — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend playwright-cli for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
playwright-cli is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
I recommend playwright-cli for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in playwright-cli — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
playwright-cli reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 47