Webapp Testing
Skill ActiveToolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
To enable users to effectively test and debug local web applications by providing Playwright-based automation scripts and utilities.
Features
- Automated local web application testing
- Server lifecycle management for development environments
- Frontend functionality verification
- UI behavior debugging
- Browser screenshot capture
- Console log viewing
Use Cases
- Testing dynamic web applications locally before deployment
- Debugging UI issues by capturing screenshots and logs
- Automating interaction with local development servers
- Verifying frontend behavior with Playwright scripts
Non-Goals
- Testing deployed or remote web applications
- End-to-end CI/CD pipeline integration
- Automated security vulnerability scanning
- Performance load testing
Trust
- warning:Issues AttentionThere are 135 open issues and 11 closed issues in the last 90 days, indicating a very low closure rate and slow maintainer response.
Versioning
- warning:Release ManagementWhile the commit history is recent, there is no explicit versioning indicated in the SKILL.md or other manifests, and installation instructions might point to 'main'.
Scope
- info:Tool surface sizeThe skill exposes a few core Python scripts and example files, which is a reasonable number for its focused purpose.
Execution
- warning:Pinned dependenciesThe Python scripts lack explicit shebangs declaring interpreter versions, and while Playwright needs to be installed, there's no explicit mention of pinning its version or lockfiles for the skill's dependencies.
Installation
First, add the marketplace
/plugin marketplace add anthropics/skills/plugin install skills@anthropic-agent-skillsQuality Score
Similar Extensions
Playwright Best Practices
100Use when writing Playwright tests, fixing flaky tests, debugging failures, implementing Page Object Model, configuring CI/CD, optimizing performance, mocking APIs, handling authentication or OAuth, testing accessibility (axe-core), file uploads/downloads, date/time mocking, WebSockets, geolocation, permissions, multi-tab/popup flows, mobile/responsive layouts, touch gestures, GraphQL, error handling, offline mode, multi-user collaboration, third-party services (payments, email verification), console error monitoring, global setup/teardown, test annotations (skip, fixme, slow), test tags (@smoke, @fast, @critical, filtering with --grep), project dependencies, security testing (XSS, CSRF, auth), performance budgets (Web Vitals, Lighthouse), iframes, component testing, canvas/WebGL, service workers/PWA, test coverage, i18n/localization, Electron apps, or browser extension testing. Covers E2E, component, API, visual, accessibility, security, Electron, and extension testing.
Develop Web Game
100Use when Codex is building or iterating on a web game (HTML/JS) and needs a reliable development + testing loop: implement small changes, run a Playwright-based test script with short input bursts and intentional pauses, inspect screenshots/text, and review console errors with render_game_to_text.
Use My Browser
100Use when work depends on the user's live browser session or visible rendered state rather than static fetches, especially for browser debugging contexts or DevTools-selected elements or requests, logged-in dashboards or CMS flows, localhost apps, forms, uploads, downloads, media inspection, DOM or iframe inspection, Shadow DOM, or browser failures that look like soft 404s, auth walls, anti-bot checks, or rate limits.
Telegram Crabbox E2e Proof
100Use when reviewing, reproducing, or proving OpenClaw Telegram behavior with a real Telegram user on Crabbox, including PR review workflows that need an agent-controlled Telegram Desktop recording, TDLib user-driver commands, Convex-leased credentials, WebVNC observation, and motion-trimmed artifacts.
Openclaw Testing
100Choose, run, rerun, or debug OpenClaw tests, CI checks, Docker E2E lanes, release validation, and the cheapest safe verification path.
Agent Browser
100Browser 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 requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.