agentsclimarketplace

Browser verification

Skill motao123/dev-workflow-kit/browser-verification

21 markdown-first software delivery workflow skills for Claude Code, Codex, and compatible agents. Standalone skill kit covering planning, debugging, CI, review, security, rollout, performance, data quality, and post-incident workflows.

Install
npx -y skills add motao123/dev-workflow-kit --skill browser-verification

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.7 KB, as published. Nobody here has run it

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

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.