533 browser automation skills from 183 authors. They drive a real browser: open pages, click through flows, fill forms and capture what happened. Half of them fit into 1 994 tokens or less — that is what one costs your context window when the agent loads it. 132 ship runnable scripts rather than instructions alone. 6 of them cannot work without an MCP server, most often rube. We also found 98 copies of these same skills sitting in other people's repositories — counted once here, not 98 times.
533 unique 183 authors 329 updated this month 66 from vendors
Automate browser interactions and web testing. Provides scriptable browser control for web scraping, testing, and automation.
> Load this skill when configuring axe-core scans, reviewing automated accessibility test results, or writing tests that use @axe-core/playwright, @axe-core/react, or similar integrations. Provides a quick reference to axe 4.x rule IDs, their WCAG mapping, and default severity levels.
Audit live URLs using Playwright and Axe combined with WCAG skills
>- Upload local images to a GitHub PR and embed them in the description or comments. Use when asked to "attach screenshots to PR", "add images to PR", "upload test results to PR", "embed screenshots in PR description", "add before/after images to PR", "attach UI screenshots", "show test results in PR", "add visual evidence to PR", or any request involving images and PRs. Always use this skill when the user wants to visually document changes in a pull request, even if they don't use the word "upload" — phrases like "put the screenshot in the PR" or "show the image in the PR" should trigger this skill. Prefers Chrome DevTools MCP (most stable) as the browser automation backend, falling back to Playwright MCP or agent-browser only when Chrome DevTools MCP is unavailable.
Use when making user-facing UI changes and you want automated screenshot walkthroughs, or at release time to compare visual changes between releases and prioritize what needs human review. Requires Playwright.