Browser QA Evidence Pack

What this skill does

Produce structured browser QA evidence for web flows, landing pages, and app screens.

It is designed for buyers who need a repeatable, auditable workflow instead of a one-off prompt. The skill asks for the minimum useful inputs, produces a structured deliverable, and includes quality gates so the result can be reviewed or handed to another teammate.

Best buyer input

A URL or local preview route, target flow, acceptance criteria, and devices/browsers to inspect.

Output contract

A QA packet with checks, screenshot checklist, console/network observations, layout issues, severity table, and retest plan.

Every run should include:

1. A short intake summary.
2. The recommended workflow or deliverable structure.
3. Evidence, assumptions, or missing-input notes.
4. A pass/fail quality checklist.
5. A next-action section the buyer can execute immediately.

Workflow

1. Clarify the buyer goal, target audience, and constraints.
2. Convert the input into a structured working brief.
3. Build the primary deliverable using the required sections from the output contract.
4. Check for gaps, contradictions, overclaims, missing data, and execution risks.
5. Return the final packet in a clean, client-ready format with a concise next step.

Quality bar

• Do not invent metrics, sources, screenshots, credentials, or platform access.
• Mark assumptions clearly when buyer input is incomplete.
• Keep private account data, access credentials, and internal-only implementation details out of the final result.
• Prefer concrete checklists, tables, and action steps over vague advice.
• Stop and ask for the missing input only when it would materially change the deliverable.

Example request

"Use this source material to create a browser qa evidence pack packet for a small team that needs a decision-ready deliverable by tomorrow."

Example result shape

• Intake summary
• Recommended structure
• Main deliverable
• QA checklist
• Risks and assumptions
• Next actions