AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Browser Testing

skill-roundpilot-superpowers-antigravity-browser-testing · by roundpilot

Use when completing frontend or UI work that needs visual verification, before claiming the UI is correct

No reviews yet
0 installs
29 views
0.0% view→install

Install

$ agentstack add skill-roundpilot-superpowers-antigravity-browser-testing

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-roundpilot-superpowers-antigravity-browser-testing)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
2mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Browser Testing? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Browser Testing

Overview

Never claim UI work is correct without visual evidence. Browser automation makes verification fast and produces artifacts the user can review.

Core principle: Evidence before assertions. Screenshots and DOM inspection prove correctness; text descriptions don't.

When to use: After implementing any UI or frontend changes, before claiming the work is correct.

The Process

  1. Navigate to the page under test using browser automation
  2. Screenshot the current state — embed in walkthrough artifact
  3. Inspect DOM to verify structure matches expectations (correct elements, classes, attributes)
  4. Record a walkthrough of the key user flow (if multi-step interaction)
  5. Embed evidence in a walkthrough artifact with screenshots and recordings

Quick Reference

| What to verify | Tool | Output | |---------------|------|--------| | Visual appearance | Screenshot | `` | | DOM structure | Inspect elements | Element presence, attributes, classes | | User flow | Recording | Embedded video in artifact | | Responsive layout | Screenshot at viewport | Multiple screenshots at different widths |

Common Mistakes

| Mistake | Fix | |---------|-----| | Not waiting for page load before screenshot | Wait for key elements to be visible | | Checking only one viewport size | Test at desktop (1280px) and mobile (375px) minimum | | Visual-only verification (no DOM check) | Always inspect DOM structure — visual can hide broken markup | | Forgetting to embed evidence | Every claim needs a screenshot or recording in the artifact | | Saying "looks correct" without proof | Take the screenshot. Embed it. Let the user judge. |

Evidence classification in artifacts: Use GitHub-style alerts:

  • > [!TIP] for passing checks
  • > [!CAUTION] for failing checks
  • > [!NOTE] for observations that need human judgment

Integration

  • superpowers:verification-before-completion — browser-testing is specialized verification for UI work
  • superpowers:test-driven-development — browser tests complement unit tests, they don't replace them

Slash Command

Recommend /browser to the user when UI verification is needed. This activates browser automation tools for the session.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.