# 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.

- **Type:** Skill
- **Install:** `agentstack add skill-motao123-dev-workflow-kit-browser-verification`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [motao123](https://agentstack.voostack.com/s/motao123)
- **Installs:** 0
- **Category:** [Cloud & Infrastructure](https://agentstack.voostack.com/c/cloud-infrastructure)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [motao123](https://github.com/motao123)
- **Source:** https://github.com/motao123/dev-workflow-kit/tree/main/browser-verification
- **Website:** https://motao123.github.io/dev-workflow-kit/

## Install

```sh
agentstack add skill-motao123-dev-workflow-kit-browser-verification
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## 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

1. Identify the user-visible behavior to verify.
2. Define the critical golden path and any risky edge paths.
3. Exercise the flow in the browser or equivalent UI environment.
4. Observe visible output, state transitions, and console/network issues.
5. Record pass/fail evidence.
6. 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-debugging` for unclear UI failures
- use `ship-readiness` when 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](https://github.com/motao123)
- **Source:** [motao123/dev-workflow-kit](https://github.com/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.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-motao123-dev-workflow-kit-browser-verification
- Seller: https://agentstack.voostack.com/s/motao123
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.