MCP CheckClaude skills for browser automation
265 public Claude skills touch on browser automation. These 50 are the closest fit, best-known sources first. Each links to its folder; copy it into ~/.claude/skills/ to use it.
anchor browser automation
Automate Anchor Browser tasks via Rube MCP (Composio). Always search tools first for current schemas.
ComposioHQ/awesome-claude-skills★ 78kNo licence statedFolder:
anchor-browser-automationinvisible playwright
Use the Dot's browser identities for any task on a website or search on the web: which identity to use, opening and closing one, and when a plain download is simpler than a browser.
feder-cr/invisible_dots★ 32kMITFolder:
invisible-playwrightplaywright expert
Use when writing E2E tests with Playwright, setting up test infrastructure, or debugging flaky browser tests. Invoke to write test scripts, create page objects, configure test fixtures, set up reporters, add CI integration, implement API mocking, or…
Jeffallan/claude-skills★ 12kMITFolder:
playwright-experthive.browser automation
Required before any hive-browser CLI command. The browser is driven from the terminal by running `hive-browser <command> ... --json` via terminal_exec — not via MCP tools. Teaches the browser lifecycle rules (the bridge attaches to the USER'S running…
aden-hive/hive★ 11kApache-2.0Folder:
browser-automationplaywright migration
Step-by-step migration guides for moving to Playwright from Cypress or Selenium/WebDriver — command mappings, architecture changes, and incremental adoption strategies.
zebbern/claude-code-guide★ 4.7kMITFolder:
migrationplaywright ci
Production-ready CI/CD configurations for Playwright — GitHub Actions, GitLab CI, CircleCI, Azure DevOps, Jenkins, Docker, parallel sharding, reporting, code coverage, and global setup/teardown.
zebbern/claude-code-guide★ 4.7kMITFolder:
ciplaywright pom
Page Object Model patterns for Playwright — when to use POM, how to structure page objects, and when fixtures or helpers are a better fit.
zebbern/claude-code-guide★ 4.7kMITFolder:
pomplaywright
Use when the task requires automating a real browser from the terminal (navigation, form filling, snapshots, screenshots, data extraction, UI-flow debugging) via `playwright-cli` or the bundled wrapper script.
foryourhealth111-pixel/Vibe-Skills★ 3.8kApache-2.0Folder:
playwrightazure resource manager playwright dotnet
Azure Resource Manager SDK for Microsoft Playwright Testing in .NET. Use for MANAGEMENT PLANE operations: creating/managing Playwright Testing workspaces, checking name availability, and managing workspace quotas via Azure Resource Manager. NOT for running…
microsoft/skills★ 3.2kMITFolder:
azure-resource-manager-playwright-dotnetazure microsoft playwright testing ts
Run Playwright tests at scale using Azure Playwright Workspaces (formerly Microsoft Playwright Testing). Use when scaling browser tests across cloud-hosted browsers, integrating with CI/CD pipelines, or publishing test results to the Azure portal.
microsoft/skills★ 3.2kMITFolder:
azure-microsoft-playwright-testing-tsbrowser automation
This skill should be used when the user asks to "build web automation scripts", "check browser automation for detection", "generate web scraping code", "create form filling automation", or "build anti-detection browser scripts".
borghei/Claude-Skills★ 1kLicence: see repoFolder:
browser-automationplaywright pro
End-to-end testing with Playwright: test generation, page objects, locator strategy, flaky- test diagnosis, visual regression, and CI integration. Use when writing E2E tests, fixing flaky tests, or migrating from Cypress/Selenium.
borghei/Claude-Skills★ 1kLicence: see repoFolder:
playwright-proqa browser automation
Browser-based QA combining Chrome MCP control with Python analysis tools. Use when performing browser QA testing, visual regression tracking, WCAG accessibility auditing, performance profiling, or health-scoring web applications.
borghei/Claude-Skills★ 1kLicence: see repoFolder:
qa-browser-automationazure playwright workspaces
Expert knowledge for Playwright Workspaces development including troubleshooting, best practices, decision making, limits & quotas, security, and configuration. Use when managing Playwright Testing workspaces, tokens/RBAC, quotas, monitoring/metrics, or…
MicrosoftDocs/Agent-Skills★ 797CC-BY-4.0Folder:
azure-playwright-workspacesplaywright best practices
Use when writing or modifying Playwright tests (.spec.ts, .test.ts with @playwright/test imports).
aiskillstore/marketplace★ 446No licence statedFolder:
playwright-best-practicesplaywright frontend
For frontend engineers authoring UI — how to make components reliably locatable by tests and AI agents. Covers the official Playwright locator priority, semantic/accessible markup first, and how to add valid, unique, stable `data-testid` attributes (naming…
testdino-hq/playwright-skill★ 405MITFolder:
frontendplaywright qa
QA engineering workflows on top of Playwright. Use when a QA engineer asks to design test cases from a ticket, PRD or acceptance criteria, decide what to automate, write a bug report from a failing test or trace, convert manual test cases (TestRail, Xray,…
testdino-hq/playwright-skill★ 405MITFolder:
qaplaywright automation
Browser automation and testing with Playwright. Use when testing web applications, automating browser tasks, taking screenshots, or validating UI behavior.
majiayu000/spellbook★ 288MITFolder:
playwright-automationskill.playwright
Use when the task requires automating a real browser from the terminal
AI45Lab/OpenART★ 260AGPL-3.0Folder:
skill.playwrightplaywright e2e
Comprehensive end-to-end testing skill using Playwright for web applications, covering page objects, selectors, assertions, waits, fixtures, and test organization.
PramodDutta/qaskills★ 244MITFolder:
playwright-e2eplaywright api
API testing skill using Playwright's built-in APIRequestContext for RESTful service validation, authentication flows, and API contract verification.
PramodDutta/qaskills★ 244MITFolder:
playwright-apiAgent Browser Automation
Fast Rust-based headless browser automation CLI with Node.js fallback for AI agents, featuring navigation, clicking, typing, snapshots, and structured commands optimized for agent workflows.
PramodDutta/qaskills★ 244MITFolder:
agent-browserapi playwright test developer
Writes and reviews API automation tests with Playwright Test, covering setup/teardown, assertions, data management, and hybrid API+UI flows. Use when creating backend API tests, contract checks, data-driven API coverage, API+UI hybrid workflows, or…
jaktestowac/awesome-copilot-for-testers★ 118MITFolder:
api-playwright-test-developermigrating tests to playwright
Migrates Cypress, Selenium, WebdriverIO, or Protractor suites to Playwright in staged slices, each with a parity gate before the old test is deleted. Use when porting a legacy browser suite, when deciding which tests are not worth porting, when a…
jaktestowac/awesome-copilot-for-testers★ 118MITFolder:
migrating-tests-to-playwrightbrowser automation expert
Expert guide for autonomous web agents (Browser-Use, Stagehand v0.4+), hardcore anti-bot evasion (Playwright Stealth, WebGL masking), and Vision LLM visual QA / Panduan ahli agen web otonom, penghindaran deteksi bot, dan QA visual berbasis Vision LLM.
roedyrustam/vibes-plug★ 116MITFolder:
browser-automation-expertplaywright ops
Playwright end-to-end testing operations - selectors, fixtures, network mocking, auth, parallelism, CI, visual regression, flake hunting. Use for: playwright, e2e test, end-to-end testing, browser test, getByRole, page object, storageState, trace viewer,…
0xDarkMatter/claude-mods★ 78MITFolder:
playwright-opscloud run puppeteer
Deploys Puppeteer browser automation on Google Cloud Run with Docker. Use when running headless browser tasks on Cloud Run, or when the user mentions Cloud Run, Puppeteer, headless Chrome, or serverless browser automation.
tranhieutt/software_development_department★ 74MITFolder:
cloud-run-puppeteerplaywright browser
Headless, reproducible browser automation with Playwright for any project — screenshots of web pages or local dev servers (desktop/tablet/mobile, full page or one element, single page or every page/menu of an app in one batch), frontend audits (console…
AndyShiu/claude-skill-playwright-browser★ 51MITFolder:
claude-skill-playwright-browsere2e playwright
Use when writing end-to-end browser tests with Playwright. Covers resilient locators, auto-waiting, network interception, authentication reuse, parallelization, and eliminating flakiness. Trigger on "write playwright tests", "e2e test is flaky", "replace…
nimadorostkar/Claude-Skills-collection★ 33MITFolder:
e2e-playwrightplaywright extension fixtures
Author the Playwright fixture layer every Chromium extension test depends on - `chromium.launchPersistentContext` with `--disable-extensions-except=$DIR` + `--load-extension=$DIR`, the `channel: 'chromium'` selection that unlocks headless extension…
testland/qa★ 13MITFolder:
playwright-extension-fixtureselectron playwright
Authors Playwright `_electron` tests for packaged Electron desktop apps - launches the app via `electron.launch({ args })`, returns an `ElectronApplication` handle, drives renderer windows as Playwright `Page` objects, and probes the main process via…
testland/qa★ 13MITFolder:
electron-playwrightelectron playwright validator
This skill should be used when a user asks to launch, inspect, automate, test, validate, or debug an Electron desktop UI through Playwright/CDP, including blank renderers, runtime import failures, accessibility snapshots, layout defects, click-through…
johnkozaris/jko-claude-plugins★ 11MITFolder:
electron-playwright-validatorplaywright network mocking
Playwright workflows for deterministic third-party responses using page.route().
hzijad/playwright-agent-skills★ 9MITFolder:
playwright-network-mockingplaywright auth state
Playwright workflows for authenticated browser state reuse through storageState and setup projects.
hzijad/playwright-agent-skills★ 9MITFolder:
playwright-auth-stateplaywright debugging
Diagnostic Playwright workflows for flaky or failing tests, including trace analysis, UI mode, and state isolation.
hzijad/playwright-agent-skills★ 9MITFolder:
playwright-debuggingplaywright stealth verify
Check whether a Playwright, Puppeteer, Selenium or CDP-driven browser presents a coherent fingerprint, using liarjs as a library against a Page you already have - navigator.webdriver, HeadlessChrome tokens, worker versus main-thread identity, patched-API…
liarjsdev/liarjs-skills★ 5MITFolder:
playwright-stealth-verifyplaywright e2e tests
Use when writing, fixing or stabilizing end-to-end or UI tests with Playwright, automating a browser user flow, replacing Cypress or Selenium tests, or setting up Playwright in a web project.
WST2002/claude-code-skills★ 3MITFolder:
playwright-e2e-testswebapp testing
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.
anthropics/skills★ 185kNo licence statedFolder:
webapp-testingdev browser
Browser automation with persistent page state. Use when users ask to navigate websites, fill forms, take screenshots, extract web data, test web apps, or automate browser workflows. Trigger phrases include "go to [url]", "click on", "fill out the form",…
code-yeongyu/oh-my-openagent★ 70kLicence: see repoFolder:
dev-browseragent browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include…
shanraisshan/claude-code-best-practice★ 68kMITFolder:
agent-browsercherry regression test
Run Cherry Studio critical-path system regression tasks through the repository-owned Playwright E2E workflow. Use for full regression, release acceptance, development-branch system validation, or a named cherry-regression-test task on GitHub-hosted macOS…
CherryHQ/cherry-studio★ 53kAGPL-3.0Folder:
cherry-regression-teste2e testing patterns
Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.
wshobson/agents★ 42kMITFolder:
e2e-testing-patternschrome devtools
Expert-level browser automation, debugging, and performance analysis using Chrome DevTools MCP. Use for interacting with web pages, capturing screenshots, analyzing network traffic, and profiling performance.
github/awesome-copilot★ 41kMITFolder:
chrome-devtoolsego browser
When you need a browser, read this Skill by default. Use it to open and operate websites, fill forms, click buttons, take screenshots, extract page data, sign in, and perform other browser automation tasks, as well as web app testing, dogfooding, QA, bug…
citrolabs/ego-lite★ 21kMITFolder:
ego-browsertiktok upload
使用仓库现有 Patchright/Playwright Chrome 上传器登录并发布 TikTok 视频。Use when 用户要发布 TikTok 视频，且当前环境可访问本仓库及其本地 Chrome 配置。
dreammis/social-auto-upload★ 16kMITFolder:
tiktok-uploadbrowser edge cases
SOP for debugging browser automation failures on complex websites. Use when browser tools fail on specific sites like LinkedIn, Twitter/X, SPAs, or sites with Shadow DOM.
aden-hive/hive★ 11kApache-2.0Folder:
browser-edge-casesbrowser cdp
Use this skill when you need to control a Chrome browser via CDP (Chrome DevTools Protocol) to reuse existing login sessions. Covers: launching Chrome in debug mode, opening URLs, waiting for page load, evaluating JavaScript, taking snapshots, and…
zenstory-ai/oh-story-claudecode★ 8.1kMITFolder:
browser-cdpreplica test
Clicks through every flow of an app clone and tests it for bugs: a test plan generated from the recon flows with happy paths and edge cases, Playwright end-to-end tests where possible, a browser click-through where not, and bug reports in a fixed format…
Jakeschincariol/replica-skill★ 6.4kMITFolder:
replica-testbrowser act
Browser automation CLI for AI agents. NEVER run browser-act commands directly via Bash — always invoke this skill first. Use browser-act when a user mentions it by name, includes or asks to run a browser-act CLI command (e.g., browser-act browser list), or…
browser-act/skills★ 6.3kMITFolder:
browser-actsn ppt doctor
Use when diagnosing PPT Skill setup or failures involving source parsing, Playwright or Chromium rendering, HTML-to-PPTX export, Workbench startup, or bundled search and image-tool configuration.
OpenSenseNova/SenseNova-Skills★ 6kMITFolder:
sn-ppt-doctor
Claude skills for browser automation: common questions
What's the best Claude skill for browser automation?
There are 265 of them, spread over 152 repositories on GitHub. Named for it and most starred: anchor browser automation (ComposioHQ/awesome-claude-skills, ★ 78k), invisible playwright (feder-cr/invisible_dots, ★ 32k) and playwright expert (Jeffallan/claude-skills, ★ 12k). Stars rate the repository a skill sits in, not the skill.
How do I install a Claude skill for browser automation?
For browser automation, take the anchor-browser-automation folder from ComposioHQ/awesome-claude-skills (the folder that holds SKILL.md) into ~/.claude/skills/ to use it in every Claude Code project, or into .claude/skills/ for one project. In the Claude apps, zip that folder and upload it as a custom skill in settings.
Are all these browser automation skills in English?
No: 2 of those listed, such as tiktok upload and browser cdp, are written mainly in Chinese, Japanese, Korean or Russian rather than English, though the browser automation task is the same. Claude can follow them either way, but read them before you install.
Should I use a skill or an MCP server for browser automation?
A skill teaches Claude a way of working; an MCP server gives it new tools, like access to browser automation itself. We list 85 MCP servers for browser automation if you need the connection.
Is there an official Anthropic skill for browser automation?
Yes: webapp testing comes from Anthropic's own skills repository. The other 264 are community-made.
Can I use these browser automation skills at work?
Of the 50 browser automation skills listed here, 40 sit in repositories under an open licence such as MIT or Apache 2.0, and 3, such as anchor browser automation and playwright best practices, state no licence at all, which legally means you may not reuse them. Check the licence file before you copy one into company work.
More topics: every “Claude skills for…” page.