Web App Testing

Before you start: read this whole install prompt, tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead before you do anything else. Prerequisites — None to install this skill — no account, no key, no payment, and its scripts are not run at install time. To USE it I need Python and Playwright (with a Chromium browser) already installed in my own environment — the skill does not install them for me — plus a local web application of mine to test: its examples only target my own servers on localhost or local file:// pages. Install "Web App Testing" for me. It tests local web applications by writing native Python Playwright scripts: for a static HTML file it reads the file to find selectors; for a dynamic app it either uses the bundled with_server.py helper to start my server, wait for its port, and run the automation, or, when the server is already running, it first inspects the rendered page (screenshot, DOM content, element lists) after waiting for network idle, identifies selectors from what it actually sees, and only then acts. Scripts use the synchronous Playwright API, launch Chromium headless, and close the browser when done; the examples cover discovering elements, automating a static page from a file:// URL, and capturing browser console logs. Repository: https://github.com/anthropics/skills (the skill is the whole skills/webapp-testing/ folder at the pinned commit: SKILL.md, LICENSE.txt, the scripts/ helper and the examples/ folder, 6 files in total) Pinned version: install the code at commit dbd4588f9e1033efb41dad4bef2f7947c8993d44 exactly. Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Clone https://github.com/anthropics/skills into a temporary folder, check out commit dbd4588f9e1033efb41dad4bef2f7947c8993d44, and copy the skills/webapp-testing/ folder from that checkout. Then compare every file in the folder with the fingerprints recorded for this listing on 2026-10-22: [FINGERPRINTS] - LICENSE.txt: SHA-256 bc6b3af2f331cbc7fb0da1344efb2cbe5877a31498b4d70dbc7000f3405a1362 - SKILL.md: SHA-256 51b7349e77ec63b7744a6f63647e7566a0b4d2e301121cc10e8c2113af6556a2 - examples/console_logging.py: SHA-256 ea46877289acb82da7e7ce59d0bc37c8977cd57e2a006d0c88d7a1c625bf95da - examples/element_discovery.py: SHA-256 d63c89604a22f8845d724e95dda45db49b1bf57c25ce0a83afbb7b8da3d402f0 - examples/static_html_automation.py: SHA-256 9d533aafb875ee3ab8b8ebf8f5b9003ac8d999da3d09b285cce252e623140064 - scripts/with_server.py: SHA-256 b0dcf4918935b795f4eda9821579b9902119235ff4447f687a30286e7d0925fd If a file does not match, it changed since the listing was prepared: do not install it yet, tell me what you found and let me decide. 2. Read SKILL.md in full, and tell me in plain words: what the skill does when used, what it connects to, whether it reads or sends any personal information or credentials, and anything that seems unusual. Stop on any red flag and tell me before going further. Confirm these points from the files: - The skill folder holds 6 files: SKILL.md, LICENSE.txt (Apache-2.0), the with_server.py helper under scripts/, and three example Python scripts under examples/ (element discovery, static HTML automation, console logging). The helper, read as part of this review, starts the server commands I give it, waits for their ports on localhost, runs my test command, then terminates the servers it started. Nothing in the folder is run during installation. - Nothing is sent anywhere during installation itself; the only download at install time is the skill folder from GitHub at the pinned commit. No server is started, no browser is launched and no page is visited during installation. - At use time, exchanges go only to my own local application: pages served on localhost or local files, in a headless browser on my machine; screenshots and DOM captures stay as my local files. No credentials are read or sent and no third-party site is targeted by the skill or its examples. - Do not run the helper or any example, do not start any server, and do not use the skill in any way during this install: using it is a separate step that only starts when I actually ask to test an app, and Playwright must already be installed by me before then. 3. When I say "yes, install", install it as a skill: copy the whole webapp-testing folder into the agent's skills directory, in a folder named exactly "webapp-testing", keeping its 6 files in their original relative layout (SKILL.md at its root). 4. Verify with no network calls: frontmatter valid (name: webapp-testing), the 6 files in place with matching fingerprints. Do not run anything from the folder and do not use the skill to verify. 5. Report what was installed, where, and what I still need to do myself (for example: that using it needs Python and Playwright already installed by me, that it only tests my own local apps on localhost or local files, and that nothing was run during this install; using the skill is a separate step that only starts when I ask for it). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.