Browser QA
Automated post-deploy UI verification with a browser automation MCP: console-error and Core Web Vitals smoke checks, interaction tests, visual regression, axe accessibility, SHIP or DO-NOT-SHIP verdict.
- What
- Automated post-deploy UI verification with a browser automation MCP: console-error and Core Web Vitals smoke checks, interaction tests, visual regression, axe accessibility, SHIP or DO-NOT-SHIP verdict.
- Cost
- Free
- Needs
- Use "Browser QA" with your Muse.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: an automated browser QA skill that verifies your deployed frontend the way a careful tester would, before you ship. Driven by a browser automation MCP (claude-in-chrome, Playwright, or Puppeteer), it runs four phases: a smoke test (console errors, 4xx/5xx network requests, above-the-fold screenshots, Core Web Vitals thresholds), an interaction test (every nav link, forms with valid and invalid data, auth flows, critical user journeys), a visual regression pass (screenshots at 375px, 768px, and 1440px compared against committed baselines, no baseline means INCONCLUSIVE never a silent pass), and an accessibility audit (axe-core, WCAG 2.2 AA, keyboard navigation, screen reader landmarks), ending in an explicit SHIP or DO-NOT-SHIP verdict. Safety is built in: read-only by default, mutating journeys only against staging with explicit opt-in, seeded test credentials never production logins, and credentials redacted from screenshots. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: requires a browser automation MCP configured (claude-in-chrome, Playwright, or Puppeteer); axe-core covers roughly a third of WCAG, the rest needs human judgment; never run mutating journeys against production. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Copy the install package below, then paste it into MuseThe install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Use "Browser QA" with your Muse. Prerequisites: a browser automation MCP configured (claude-in-chrome, Playwright, or Puppeteer) and a deployed staging or preview URL. Pure workflow guidance, nothing to install. 1. Open the skill: https://github.com/affaan-m/ECC/blob/main/skills/browser-qa/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Run post-deploy QA on [staging URL]: smoke, interaction, visual regression, accessibility. Give me a SHIP or DO-NOT-SHIP verdict." 3. For PR reviews, add: "Focus on the pages touched by this PR and compare against the committed baselines." Tip: commit baseline screenshots first; without them the visual pass reports INCONCLUSIVE. Safety: a skill is plain-text instructions; it drives a real browser, so keep it read-only against production, use seeded test credentials, and redact any credentials from saved screenshots.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.