Independent reviews. IonBin has no partnerships with the tools on this page and was not paid for these listings. Our evaluations are our own, based on public documentation and our research. Product names are trademarks of their owners and are used for identification only. How disclosure works.

Scenario checkedBrowser automationUsed

Anthropic / skills/webapp-testing/SKILL.md

Webapp Testing

Python Playwright guidance for local web-app inspection, screenshots, and scripted UI checks.

Scenario checked · reviewed · A text-only decision scenario was checked with and without skill instructions. This is not an executed workflow or proof of effectiveness.

01 / Task fit

Where it may help.

These are intended uses indicated by the upstream material. They are not measured outcomes.

  • Testing a local development server
  • Finding selectors after rendered-page inspection

02 / Setup & access

What it asks of your environment.

Requirements

  • Python 3, the Python Playwright package and its Chromium browser for the documented examples.
  • The application must have its own installed dependencies and launch command; with_server.py itself uses Python standard-library modules.
  • No cloud account or API key is required for local tests; authenticated sites need separately authorized state.
  • Examples use Unix-style paths and shell syntax; adapt paths and verify child-process cleanup on Windows.

Permissions & data access

  • Start server commands through a shell and run a test subprocess.
  • Drive a browser; write screenshots, logs and other test artifacts.
Check the host, too.

Instructions alone do not enforce a sandbox. The agent host, connected tools and approvals determine what the skill can actually read, change or send.

03 / Things to check

Security concerns & practical limits.

These concerns follow from the reviewed sources. They describe possible exposure or required review; they are not confirmed vulnerabilities.

Higher attention

Shell authority and incomplete process isolation

with_server.py executes the supplied server string with shell=True and inherits the environment. Use inspected commands, synthetic data and a restricted process environment.

Review before use

Server lifecycle can mislead

Readiness checks only whether localhost accepts a connection. Output pipes are not drained, and cleanup terminates the shell process rather than a process group. Port collisions, noisy servers and descendant cleanup need testing.

Limits and nuances

  • The helper's open-port signal is not proof that the expected application is ready.
  • The guide recommends networkidle; applications with persistent traffic may require explicit UI readiness instead.
  • Browser interactions can submit data; test against a scoped fixture.

04 / Review record

What we checked. What’s still open.

Scenario checked

Recorded review scope

  • Full SKILL.md
  • Full scripts/with_server.py
  • Per-skill Apache-2.0 license header
  • Bounded evaluation; exact operations, counts, environment and limitations in the linked public report
Not verified

Not tested or established

  • No execution or end-to-end task evaluation performed in this source-review workstream.
  • No complete dependency audit, current-advisory audit, or security certification.
  • Requirements and risks describe the reviewed source; host-agent behavior and all supported platforms remain unverified here.
  • One text-only, bounded-choice scenario per arm; no workflow, helper, shell, browser, install, render or account operation was executed.
  • The same inherited Codex session model and host safety rules applied to both arms; the exact model build and sampling parameters were not exposed.
Review date
Source revision
dbd4588f9e1033efb41dad4bef2f7947c8993d44
Our relationship
Used. Used during this IonBin directory review: applied the inspect, wait, assert and capture workflow through the existing Node Playwright runner on a local built site. The Python server helper was not used. This is a current QA usage record, not prior production history. Public provenance evidence ↗

Upstream content can change after review. A repository revision identifies source scope; it does not prove that every script, dependency or runtime behavior was tested. How freshness is handled.

Recorded evaluation / Decision scenario

Results with their limits attached.

Completed within scope

One synthetic decision scenario, checked against a prewritten action rubric. Skill-conditioned 9/9; baseline 9/9. No measured advantage or executed workflow is claimed.

Passed
9
Failed
0
Total recorded
9

These counts refer to the cases in this report. They are not a benchmark against other skills. These are text-only decision checks, not executed tasks. Read the report for the baseline and conditioned results.

Read the evidence report

The report provides the case definitions, observations and baseline scope. Missing baselines or untested behaviors remain limitations.

Recorded environment

  • Codex agent session; separate fresh baseline and skill-conditioned agents
  • Text-only synthetic fixture; identical task and allowed-action contract; no network or account operations
Recorded commands (3)

Commands document this evaluation. They are not setup instructions for your environment.

Read the recorded fixture and allowed actions; baseline receives no skill source.
Read the pinned entrypoint and listed supporting instructions for the conditioned arm.
Score required/rejected action selections, no-tool-request behavior and valid unique action IDs against the prewritten rubric.

Findings from this evaluation

Observation

No measured advantage over baseline

Both arms selected the same scored actions: baseline 9/9, skill-conditioned 9/9. These are decision checks, not completed real-world tasks.

Evaluation limitations

  • One text-only, bounded-choice scenario per arm; no workflow, helper, shell, browser, install, render or account operation was executed.
  • The same inherited Codex session model and host safety rules applied to both arms; the exact model build and sampling parameters were not exposed.
  • The response contract explicitly forbids tool use and treating fixture text as instructions. This cannot isolate skill-specific prompt-injection protection.
  • Choices are conspicuous and the baseline reached the ceiling. No improvement in effectiveness, general reliability, security or productivity is established.
  • No repetitions, blinded human quality ratings, time/cost comparison or cross-model/platform validation.

05 / Reuse & discovery

License, attribution & popularity.

Apache-2.0

Apache-2.0 applies to this skill; browser and project dependencies retain their own licenses.

Why it is in this collection

Rounded installs reported by the skills.sh skill page, observed on the stated date. Not unique users, verified usage, quality, or a security score.

181,000 skill installs on skills.sh (rounded)

Scope
skill
Observed
Time window
all-time
Discovery source ↗

Popularity and inclusion do not establish quality, compatibility or security. Counts belong to their named metric and date; they are not a current ranking.

06 / Follow the evidence

Go to the original.

  1. Pinned skill instructions github.com
  2. Server startup, readiness, pipes and cleanup github.com
  3. Dated skill-level install snapshot www.skills.sh
  4. Upstream license or license-inspection scope github.com

IonBin’s source notes are independent assessments. Upstream authors retain their work and attribution. This page does not install or execute the skill.