Browser QA — Automated Visual Testing & Interaction

Use this skill to automate visual testing and UI interaction verification using browser automation after deploying features.

You say
Buy it · $29 Read it before you buy $29 Written by affaan-m · unverified publisher
Context cost
925 tokensestimated from the bundle, loaded when it triggers
Bundle
1 file · 3.7 kBtext throughout, nothing executable
Licence
MITpaid listing
Last change
no release on file
Servers it uses
Noneruns standalone

What it does

Use this skill to automate visual testing and UI interaction verification using browser automation after deploying features.

Installed, it changes the agent in these ways.

What this skill changes about the agent is not written down here yet. The listing was collected from its source, and the description is in its own SKILL.md.

Workflow

Runs a procedure end to end.

browserautomationtesting

The skill itself

This is the whole product. A skill is instructions the model reads, so there is nothing behind the listing you cannot see first — the front matter loads with every session, and the body below it loads when the skill triggers.

SKILL.md3.7 kB · 106 lines
--- name: browser-qa description: Use this skill to automate visual testing and UI interaction verification using browser automation after deploying features. metadata: origin: ECC ---
8# Browser QA — Automated Visual Testing & Interaction
9
10## When to Use
11
12- After deploying a feature to staging/preview
13- When you need to verify UI behavior across pages
14- Before shipping — confirm layouts, forms, interactions actually work
15- When reviewing PRs that touch frontend code
16- Accessibility audits and responsive testing
17
18## How It Works
19
20Uses the browser automation MCP (claude-in-chrome, Playwright, or Puppeteer) to interact with live pages like a real user.
21
22### Safety first — blast radius (run read-only by default)
23
24Browser QA drives real auth and real user journeys, so treat the blast radius explicitly.
25Default to **read-only**: never run a **mutating** journey (checkout, payment, delete,
26mass-update) against a production URL — require an explicit opt-in **and** a staging/preview
27URL. Use seeded **test credentials**, never real production logins, and **redact**
28credentials/tokens/PII before saving any screenshot.
29
30### Phase 1: Smoke Test
31```
321. Navigate to target URL
332. Check for console errors (filter noise: analytics, third-party)
343. Verify no 4xx/5xx in network requests
354. Screenshot above-the-fold on desktop + mobile viewport
365. Check Core Web Vitals: LCP < 2.5s, CLS < 0.1, INP < 200ms
37 (INP replaced FID in March 2024; thresholds per web.dev)
38```
39
40### Phase 2: Interaction Test
41```
421. Click every nav link — verify no dead links
432. Submit forms with valid data — verify success state
443. Submit forms with invalid data — verify error state
454. Test auth flow: login → protected page → logout (test creds only, never prod)
465. Test critical user journeys (checkout, onboarding, search)
47 — read-only by default; only exercise mutating journeys against staging
48 with explicit opt-in (see "Safety first" above)
49```
50
51### Phase 3: Visual Regression
52```
531. Screenshot key pages at 3 breakpoints (375px, 768px, 1440px)
542. Compare against committed baseline screenshots
55 — no baseline ⇒ report INCONCLUSIVE, never a silent PASS
563. Flag layout shifts > 5px, missing elements, overflow
574. Check dark mode if applicable
58```
59
60### Phase 4: Accessibility
61```
621. Run axe-core or equivalent on each page
632. Flag WCAG 2.2 AA violations (contrast, labels, focus order)
643. Verify keyboard navigation works end-to-end
654. Check screen reader landmarks
66```
67
68> Note: axe-core automatically covers roughly 30–40% of WCAG. A clean run is **necessary,
69> not sufficient** — keyboard nav, focus order, and a screen-reader pass still need a manual
70> check. Don't report "accessible" from an automated pass alone.
71
72## Output Format
73
74```markdown
75## QA Report — [URL] — [timestamp]
76
77### Smoke Test
78- Console errors: 0 critical, 2 warnings (analytics noise)
79- Network: all 200/304, no failures
80- Core Web Vitals: LCP 1.2s ✓, CLS 0.02 ✓, INP 89ms ✓
81
82### Interactions
83- [✓] Nav links: 12/12 working
84- [✗] Contact form: missing error state for invalid email
85- [✓] Auth flow: login/logout working
86
87### Visual
88- [✗] Hero section overflows on 375px viewport
89- [✓] Dark mode: all pages consistent
90
91### Accessibility
92- 2 AA violations: missing alt text on hero image, low contrast on footer links
93
94### Verdict: SHIP WITH FIXES (2 issues, 0 blockers)
95# verdict ∈ SHIP / SHIP WITH FIXES / DO NOT SHIP; use INCONCLUSIVE if no visual baseline
96```
97
98## Integration
99
100Works with any browser MCP:
101- mChild__claude-in-chrome__* tools (preferred — uses your actual Chrome)
102- Playwright via mcp__browserbase__*
103- Direct Puppeteer scripts
104
105Pair with /canary-watch for post-deploy monitoring.
106
In the file
SKILL.md583 words
Files1
LicenceMIT
Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈50
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
875
on trigger
The instruction body, read only when the skill fires.
0.46%
of a 200k window
Ten skills this size would take about 5% of the window before you open a file.
050k100k150k200k context window

925 tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Small enough to keep loaded permanently without thinking about it.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

Adoption
Installsnone yet
Ratingno reviews yet

The procedure it runs

The procedure has not been published here. It is in the skill’s own SKILL.md, which its author has not sent to the marketplace yet.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

It writes no files and reaches no network. All it changes is how the model reasons and writes.

What it asks for
Writes filesno
Network accessno

Read from the allowed-tools line of this skill’s own SKILL.md. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

What is in the bundle

1 file, 3.7 kB on disk. A bundle is text throughout: the instructions the model reads, plus the templates it fills in.

  • SKILL.md3.7 kB
What is not in it

No dependencies and nothing executable: a skill is text the agent reads, so the bundle is 1 file you can review in full before installing. The MIT licence covers the templates and examples as well as the instructions.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

$29 once
Browser QA — Automated Visual Testing & Interaction · MIT · affaan-m
one-time
Price$29 once
LicenceMIT — the author’s, unchanged by this purchase
Paid throughStripe, once, on the card you add at the checkout
Keeps workingfor good — the files are yours once they are on disk
Updatesevery update its author ships, delivered through this account

You can read the whole bundle before paying — the SKILL.md above is the product, not a preview of it. What the money buys is the delivery: the folder packaged and handed to your machine by key, every update its author ships, and our support if it does not do what this listing says. The terms of use are MIT, set by the author and unchanged by buying it here.

Payment runs through Stripe, on a page like this one rather than a redirect. Once there is an account it joins the same mcprush invoice as everything else you run, so there is never a second card to enter.

Which clients pick it up on their own

A skill is a folder of text. A client with a skills folder reads it without being told; everywhere else the same text works, it is just handed to the model rather than found.

Claude Code.claude/skills/
Claude Desktop
ChatGPT
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok.grok/skills/
Zed.agents/skills/
Windsurf.windsurf/skills/
Agent SDK.claude/skills/
HTTP / API
This release
Versionnot versioned
Publishedno release date on file
Price$29
Referenceaffaan-m/browser-qa-automated-visual-testing-interaction

Versions

Its author publishes no version number, so there is nothing here to pin to: what you install is the folder as it stands today. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

v
  • No earlier releases have been published to the marketplace.
Pinning

Nothing to pin to: this skill carries no version number of its own. What you install is what the folder holds on the day you install it.

Reviews

no reviews yet · no installs yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Who can post

Only accounts that have had the skill installed for fourteen days, so a review is written after living with it rather than after reading it. Publishers may reply once.

Publisher
Servers0