MCP CheckClaude skills for web app testing
The 50 strongest of 315 web app testing skills on GitHub. Skills built for web app testing come first; no repository gets more than 3 spots. Each links to its folder; copy it into ~/.claude/skills/ to use it.
browser testing with devtools
Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real…
addyosmani/agent-skills★ 112kMITFolder:
browser-testing-with-devtoolsadd product e2e eval
Add or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution.
paperclipai/paperclip★ 109kMITFolder:
add-product-e2e-evale2e 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-patternsinvisible 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-experte2e seo assistant
Full SEO workflow covering technical audits, content gaps, backlink opportunities, on-page fixes, and content briefs. Use when given a site and target keywords to get complete SEO analysis and actionable content plans. End-to-end SEO in one skill.…
irinabuht12-oss/marketing-skills★ 6.1kNo licence statedFolder:
e2e-seo-assistantplaywright 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-tse2e setup
Set up an end-to-end test suite in any repo, following practices that make e2e a reliable per-PR gate: real flows over bypass, layered assertions, a reusable auth/session helper, video+trace evidence, and a compounding suite. Use when a repo has no e2e (or…
AI-Builder-Club/skills★ 1.3kNo licence statedFolder:
e2e-setupbrowser testing with screenshots
Use when testing web applications with visual verification - automates Chrome browser interactions, element selection, and screenshot capture for confirming UI functionality
AgentWorkforce/relay★ 1.1kApache-2.0Folder:
browser-testing-with-screenshotsplaywright 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-proe2e red triage
Classify one unexpected end-to-end test failure as a product defect or an environment fault needing a new preflight check. MANUAL-ONLY: load when the suite runner names a specific failure. NEVER auto-load from context.
sno-ai/sno-station-skills★ 884Apache-2.0Folder:
e2e-red-triagee2e environment preflight
Check external services, hosts, browser sessions, model endpoints, and agents before an end-to-end run. MANUAL-ONLY: load when a caller names it. NEVER auto-load from context for ordinary testing or debugging.
sno-ai/sno-station-skills★ 884Apache-2.0Folder:
e2e-environment-preflightazure 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-workspacesintegration e2e testing
Defines integration/E2E skeleton annotations, lane and file contracts, and route-parity review criteria. Use when generating or consuming test skeletons or reviewing shared mutation routes.
shinpr/claude-code-workflows★ 706MITFolder:
integration-e2e-testingpatrol e2e testing
Use when writing E2E/integration tests, testing native interactions like permissions or system dialogs, capturing UI regressions, or validating cross-platform behavior (Patrol 4.x).
evanca/flutter-ai-rules★ 665MITFolder:
patrol-e2e-testingplaywright 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:
qabrowser test loop
Use to actually verify a web change in a real browser instead of assuming it works — click through a flow, catch console errors, check a form submits, confirm a fix on the page. Trigger when a UI change needs proof, a bug only reproduces in the browser, or…
OneWave-AI/claude-skills★ 398MITFolder:
browser-test-loope2e testing
Use when writing or stabilizing Playwright tests that drive a real browser through multi-step journeys — durable locators, web-first assertions, storageState auth, trace/retries, and flakes that only bite in CI. NOT in-process component tests (that is…
ericrisco/rsc-harness★ 388MITFolder:
e2e-testingrun dashboard e2e local changes
Run Playwright E2E (tests/e2e/) against the docker/ all-in-one harness so it reflects LOCAL code changes, not a stale cached image.
BlackBeltTechnology/pi-agent-dashboard★ 337MITFolder:
run-dashboard-e2e-local-changesplaywright 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-automationcross browser testing
Use this skill when you need to select evidence-backed browser, engine, device, and version coverage; triggers include 跨浏览器测试 and cross-browser testing.
naodeng/awesome-qa-skills★ 288Licence: see repoFolder:
cross-browser-testingskill.playwright
Use when the task requires automating a real browser from the terminal
AI45Lab/OpenART★ 260AGPL-3.0Folder:
skill.playwrightcypress e2e
End-to-end testing skill using Cypress for web applications, covering custom commands, network intercepts, fixtures, cy.session, and component testing patterns.
PramodDutta/qaskills★ 244MITFolder:
cypress-e2ee2e testing claude code
Make Claude Code write and maintain end-to-end tests like a senior SDET — Playwright and Cypress flows with stable locators, the Page Object Model, fixtures, reused auth state, network mocking, and flake-free CI. Claude Code E2E testing, done right.
PramodDutta/qaskills★ 244MITFolder:
e2e-testing-claude-codeplaywright 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-e2eagentic browser testing
Goal-driven E2E testing where a browser agent (Playwright MCP / computer-use) reads a natural-language goal and explores the app via the accessibility tree to assert outcomes — no pre-written script. Covers when intent-driven beats scripted, making agent…
petrkindlmann/qa-skills★ 228MITFolder:
agentic-browser-testinge2e run
Run the Playwright end-to-end test suite.
Goldziher/ai-rulez★ 165MITFolder:
e2e-runapi 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-playwrighte2e testing expert
Expert guide for End-to-End (E2E) testing with Playwright 1.50+, Clock API, ARIA snapshots, test fixtures, and Vitest 3+ / Panduan ahli pengujian E2E dengan Playwright 1.50+, Clock API, ARIA snapshots, dan Vitest 3+.
roedyrustam/vibes-plug★ 116MITFolder:
e2e-testing-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-opsproof e2e
Build E2E test specs for critical user journeys — Playwright or Cypress, page objects, setup/teardown, CI config. Use when asked to "write E2E tests", "end-to-end testing", "browser tests", "UI tests", or "Playwright tests".
tonone-ai/tonone★ 76MITFolder:
proof-e2eopenskills e2e test runbook
Run deterministic OpenSkills end-to-end validation across runtime tests and example agents, then report tool calls, activation behavior, and regressions.
Geeksfino/openskills★ 71Apache-2.0Folder:
openskills-e2e-test-runbookqwik e2e verification
Use when creating, modifying, debugging, or running Qwik Playwright e2e tests under e2e/, including router, adapters, docs, CLI, and React integration suites.
modem-dev/ossrules★ 64MITFolder:
qwik-e2e-verificationbrowser testing
Use when building, debugging, or verifying browser-rendered code, or running browser tests for PR- or branch-affected pages. Not for source, remote-system, credential, publish, or deploy changes.
OutlineDriven/outline-driven-development★ 55Apache-2.0Folder:
browser-testingautomated e2e testing
Turn manual cases into Playwright E2E automation run in a browser: page objects, helpers, bug evidence, reports. Not for: API tests, exploratory sessions, bug root-cause. 将手动用例转为 Playwright E2E 自动化并真实执行；含写自动化前的业务熟悉踩点、Page Object/Helper、Bug 证据与报告条目。不用于：API…
fishzjp/qa-skills★ 54MITFolder:
automated-e2e-testingplaywright 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-playwrightfec e2e testing
用于创建、维护、调试或审查真实浏览器端到端测试，包括 Playwright/Cypress、Page Object、CI 产物、trace、不稳定用例、跨页面视觉回归以及登录、支付、权限或 CRUD 等关键用户旅程。若是测试层规划或靠近 UI 组件的测试，先选择对应测试工作流；中文触发词包括 E2E、端到端测试、Playwright、Cypress。
bovinphang/frontend-craft★ 22MITFolder:
fec-e2e-testingplaywright 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-mocking
Claude skills for web app testing: before you install one
Which Claude skill should I use for web app testing?
Yes: 315 public skills from 165 GitHub repositories mention web app testing. The best-known ones named for it are browser testing with devtools (addyosmani/agent-skills, ★ 112k), add product e2e eval (paperclipai/paperclip, ★ 109k) and e2e testing patterns (wshobson/agents, ★ 42k). Stars belong to the whole repository, not to one skill.
How do I add browser testing with devtools to Claude?
For web app testing, copy the browser-testing-with-devtools folder from addyosmani/agent-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. For the Claude apps, upload the zipped folder as a custom skill instead.
What licences do these web app testing skills use?
Of the 50 web app testing skills listed here, 43 sit in repositories under an open licence such as MIT or Apache 2.0, and 3, such as e2e seo assistant and e2e setup, state no licence at all, which legally means you may not reuse them. The licence badge on each card tells you which is which.
Does Anthropic make an official web app testing skill?
Yes: webapp testing comes from Anthropic's own skills repository. The other 314 are community-made.
How recently were web app testing skills updated?
219 of the 315 web app testing skills sit in repositories that changed in the 30 days before 31 Oct 2026.
More topics: every “Claude skills for…” page.