webapp-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.

by anthropics 177k GitHub stars Complete terms in LICENSE.txt Updated Sep 10, 2026
Official↑ GrowingActive Testing Claude Code ⚠ No license
webapp-testing skill by anthropics
webapp-testing — Testing skill by anthropics

Overview

webapp-testing is an open-source testing skill for Claude Code and compatible agents, published by anthropics. Its author describes it as: “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.”. The project has 177k stars on GitHub and ships custom license terms, so review them before reuse. Add it to your setup with `/plugin marketplace add anthropics/skills`.

What webapp-testing does

To test local web applications, write native Python Playwright scripts.

Best for

What’s inside

The SKILL.md for webapp-testing is organised into these sections:

  • Decision Tree: Choosing Your Approach
  • Example: Using withserver.py
  • Reconnaissance-Then-Action Pattern
  • Common Pitfall
  • Best Practices
  • Reference Files

Installation

Add webapp-testing to your agent with:

/plugin marketplace add anthropics/skills

Review a skill’s source before installing it — skills can instruct your agent to run commands. This command comes from the skill’s public repository, which is the source of truth for setup steps. New to skills? Read how to install Claude Code skills.

Supported agents

  • Claude Code — ships a claude code plugin marketplace

License

anthropics has not declared a standard open-source license for this repository (Complete terms in LICENSE.txt). Confirm the terms with the author before reusing it.

Strengths

  • Ships in anthropics/skills, an established project with 177,416 GitHub stars
  • Works with Claude Code
  • Actively maintained — repository updated in the last 30 days
  • Its repository gained 12,054 GitHub stars over the last 52 days

Things to check

  • No license declared — confirm terms with the author before reuse

Author

anthropics 21 skills in the catalog · GitHub profile ↗
View skills

Topics

Need a skill like this, tailored to your team?Build a custom skill →

Frequently asked questions

What does webapp-testing do?
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.
How do I install webapp-testing?
Run /plugin marketplace add anthropics/skills in your agent, then reload your skills. Review the source at https://github.com/anthropics/skills before installing.
Is webapp-testing free to use?
webapp-testing is publicly available on GitHub, but anthropics has not declared a standard open-source license (Complete terms in LICENSE.txt). Confirm the terms with the author before reusing it.
Which agents does webapp-testing work with?
webapp-testing lists Claude Code — named in its SKILL.md, its plugin marketplace or its repository topics. Skills use the portable SKILL.md format, so other agents that read that format may load it too.
Where does webapp-testing come from?
webapp-testing ships inside anthropics/skills, a repository that contains 21 catalogued skills in total. The repository's 177,416 GitHub stars apply to that whole collection, not to this skill on its own.

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

Official↑ GrowingActive Claude Code
177k GitHub stars No license Updated Sep 10, 2026 Free

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 runtime data. Requires the chrome-devtools MCP server to be configured.

🔥 TrendingActive Claude CodeCodexCursor+1
98k GitHub stars MIT Updated Sep 20, 2026 Free

Subjects every non-trivial decision to a fresh-context adversarial review before it stands. Use when you want every assumption cross-examined before proceeding, when stress-testing a plan for hidden failure modes, when correctness matters more than speed, when working in unfamiliar code, when stakes are high (production auth, security-sensitive logic, a high-stakes migration, irreversible operations), or any time a confident output would be cheaper to verify now than to debug later.

↑ GrowingActive Claude CodeCodexCursor+1
98k GitHub stars MIT Updated Sep 20, 2026 Free

Refines raw ideas into sharp, actionable concepts through structured divergent and convergent thinking. Use when an idea is still vague, when you need to stress-test assumptions before committing to a plan, or when you want to expand options before converging on one. Triggers on "ideate", "refine this idea", or "stress-test my plan".

↑ GrowingActive Claude CodeCodexCursor+1
98k GitHub stars MIT Updated Sep 20, 2026 Free

Drives development with tests using the red-green-refactor loop. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.

↑ GrowingActive Claude CodeCodexCursor+1
98k GitHub stars MIT Updated Sep 20, 2026 Free