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

Browser Verification

skill-markoblogo-abvx-agent-skills-browser-verification · by markoblogo

Verify frontend changes in a real browser, including layout, console errors, responsive states, network failures, screenshots, and interactions. Use after local or deployed web UI changes, visual fixes, forms, navigation, asset updates, canvas or 3D work, or whenever browser verification should replace static guessing.

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

Install

$ agentstack add skill-markoblogo-abvx-agent-skills-browser-verification

✓ 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-markoblogo-abvx-agent-skills-browser-verification)

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 Verification? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Browser Verification

Trust the browser, not static guesses. Use real rendering for frontend claims.

Setup

Prefer the repo's existing Playwright setup. If none exists, install browser tooling in a local tool directory or temporary environment rather than adding a production dependency.

Use a local static or dev server when file URLs would not match production behavior.

For security review of live targets, request routing through authorized-security-router first so scope, allowed actions, and non-destructive boundaries are explicit.

Verification Loop

  1. Start the app or static server.
  2. Open the target URL in a browser-controlled session.
  3. Check console errors and failed network requests.
  4. Verify key selectors render and have nonzero bounding boxes.
  5. Verify images/assets are complete and natural dimensions are nonzero.
  6. Check desktop and mobile viewports.
  7. Check horizontal overflow: document.documentElement.scrollWidth <= innerWidth + 1.
  8. Exercise the primary interaction path.
  9. Capture screenshots only when useful for review or debugging.
  10. Stop local servers before finalizing.

Common Assertions

  • page loaded with expected title or heading;
  • no failed requests for CSS, JS, images, fonts, or data;
  • no severe console errors;
  • target controls are visible and enabled;
  • form submission or navigation reaches expected state;
  • responsive layout has no text overlap or horizontal scroll;
  • animated/canvas/3D surfaces have nonblank rendered pixels when relevant.

Guardrails

  • Do not commit local Playwright tooling unless the repo already owns browser tests.
  • Do not claim visual verification if only static checks ran.
  • If browser install fails, report the fallback checks honestly.
  • For authenticated or paid flows, avoid real side effects unless explicitly approved.

Final Report

Include URLs, viewports, checks run, commands, failures found, and whether screenshots were captured.

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.