Browser Verification
Use when a change needs browser-level evidence such as UI flow checks, form interaction validation, console inspection, or end-to-end smoke verification. This skill focuses on observable behavior instead of code assumptions.
Install
$ agentstack add skill-motao123-dev-workflow-kit-browser-verification ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo 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.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-motao123-dev-workflow-kit-browser-verification) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
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 →About
Browser Verification
Use this skill when correctness must be demonstrated through browser behavior.
Trigger Conditions
Use this skill when:
- the task changes frontend or web UI behavior
- a form, modal, navigation, or interaction flow must be checked
- screenshots, observations, or console inspection matter
- the user asks for smoke or browser verification
- automated unit tests are not enough to prove the golden path
Do not use this skill for backend-only changes with no user-visible surface.
Workflow
- Identify the user-visible behavior to verify.
- Define the critical golden path and any risky edge paths.
- Exercise the flow in the browser or equivalent UI environment.
- Observe visible output, state transitions, and console/network issues.
- Record pass/fail evidence.
- Note remaining gaps if browser access is unavailable.
Output
For non-trivial work, provide:
- flows checked
- observations
- errors found or absence of errors
- evidence type used
- remaining gaps
Coordination
After verification:
- move into the active implementation workflow if fixes are needed
- use
systematic-debuggingfor unclear UI failures - use
ship-readinesswhen browser checks are part of release gates
Invocation Examples
- "Use browser-verification to smoke test this new form flow."
- "Use browser-verification and check the golden path plus console errors."
- "Use browser-verification for this UI regression before we call it done."
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: motao123
- Source: motao123/dev-workflow-kit
- License: MIT
- Homepage: https://motao123.github.io/dev-workflow-kit/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.