Playwright-based browser automation for reliable web testing, scraping, and agent interactions.
Works with
Emphasizes user-facing locators and Playwright's auto-wait mechanism to eliminate flaky selectors and arbitrary timeouts
Enforces test isolation patterns with fresh state per test and stealth plugins to avoid detection systems
Covers anti-patterns including CSS/XPath-first selection, single browser contexts, and manual wait calls
Includes sharp-edge guidance on traces, viewport consiste
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionbrowser-automationExecute the skills CLI command in your project's root directory to begin installation:
Fetches browser-automation from sickn33/antigravity-awesome-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 browser-automation. Access via /browser-automation 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
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
2
total installs
2
this week
31.1K
GitHub stars
0
upvotes
Run in your terminal
2
installs
2
this week
31.1K
stars
You are a browser automation expert who has debugged thousands of flaky tests and built scrapers that run for years without breaking. You've seen the evolution from Selenium to Puppeteer to Playwright and understand exactly when each tool shines.
Your core insight: Most automation failures come from three sources - bad selectors, missing waits, and detection systems. You teach people to think like the browser, use the right selectors, and let Playwright's auto-wait do its job.
For scraping, yo
Each test runs in complete isolation with fresh state
Select elements the way users see them
Let Playwright wait automatically, never add manual waits
| Issue | Severity | Solution |
|---|---|---|
| Issue | critical | # REMOVE all waitForTimeout calls |
| Issue | high | # Use user-facing locators instead: |
| Issue | high | # Use stealth plugins: |
| Issue | high | # Each test must be fully isolated: |
| Issue | medium | # Enable traces for failures: |
| Issue | medium | # Set consistent viewport: |
| Issue | high | # Add delays between requests: |
| Issue | medium | # Wait for popup BEFORE triggering it: |
Works well with: agent-tool-builder, workflow-automation, computer-use-agents, test-architect
This skill is applicable to execute the workflow or actions described in the overview.
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
sickn33/antigravity-awesome-skills
manaflow-ai/cmux
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
I recommend browser-automation for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
We added browser-automation from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
browser-automation reduced setup friction for our internal harness; good balance of opinion and flexibility.
browser-automation fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
browser-automation is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
I recommend browser-automation for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Registry listing for browser-automation matched our evaluation — installs cleanly and behaves as described in the markdown.
Keeps context tight: browser-automation is the kind of skill you can hand to a new teammate without a long onboarding doc.
Useful defaults in browser-automation — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
browser-automation reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 47