qa
QA skill uses real browser automation to test websites end-to-end, capturing visual evidence and validating user flows. It audits pages systematically, scores site health across console errors and interactivity, then fixes issues atomically with commit-per-fix discipline.
QA skill tests websites with real browser automation to find bugs, broken links, and visual issues.
AI-generated summary based on this skill's SKILL.md
Decision gist · record as of 2026-05-31
QA skill tests websites with real browser automation to find bugs, broken links, and visual issues. QA skill uses real browser automation to test websites end-to-end, capturing visual evidence and validating user flows. It audits pages systematically, scores site health across console errors and interactivity, then fixes issues atomically with commit-per-fix discipline.
Use it when
- QA captures screenshots during automated testing runs and logs visual anomalies alongside console errors.
- Yes.
Verify before relying
Read SKILL.md below before installing (1 file). Open directory: indexed for reading, not audited.
Install
blueberrycongee/termcanvas/qa · repository language: TypeScript
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
Frequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
What can QA test this website for bugs?
QA uses real browser automation to systematically test websites for bugs, broken links, and visual issues. It validates end-to-end user flows like signup, login, and checkout, captures screenshots and console errors as evidence, and generates a health score report across console health, link integrity, interactivity, and layout quality.
How does QA check for visual bugs on my page?
QA captures screenshots during automated testing runs and logs visual anomalies alongside console errors. It audits pages for layout problems, broken UI elements, and rendering issues, then documents findings with visual evidence to help you understand exactly what went wrong and where.
Can QA verify user flows like signup and checkout?
Yes. QA automates real user flows end-to-end—signup, login, checkout, and custom workflows—using browser automation. It validates that each step completes successfully, captures interactions and errors, and reports whether critical paths work as expected after deployment or code changes.
Does QA find broken links and console errors?
QA systematically crawls your site to find broken links and monitors the browser console for errors and warnings. It compiles these findings into a health score report that shows console health, link status, interactivity success, and layout integrity across your entire page or flow.
How does QA validate UI changes after deploy?
QA uses browser automation to verify UI changes work as intended after deployment. It runs automated tests on your live site, captures visual evidence of the updated interface, checks that interactions still function, and confirms the deploy looks good before you declare it production-ready.
What does QA's health score report include?
QA's health score aggregates findings across four dimensions: console errors and warnings, link validity, user interaction success, and layout correctness. The report gives you a single score plus detailed breakdowns so you can prioritize fixes and track improvement over time.
SKILL.md
Rendered from the published skill. Quoted content, verbatim.
QA
Browser-based QA testing with the browse CLI. Test real user flows, capture
visual evidence, and fix issues with atomic commits.
Phase 0: Setup
- Verify browse is available:
browse status - If not found, report error — browse binary must be installed
- Get the target URL from the task description or ask the user
Phase 1: Orient
- Navigate to the target:
browse goto <url> - Take a baseline snapshot:
browse snapshot -i - Check console for errors:
browse console - Extract navigation links:
browse links - Build a site map of pages to test (limit to 10 most important pages)
Phase 2: Page-by-Page Audit
For each page in the site map:
- Navigate:
browse goto <page-url> - Snapshot interactive elements:
browse snapshot -i - Check console for errors:
browse console - Screenshot for evidence:
browse screenshot <page-name>.png - Note issues found: broken links, console
(truncated - see the full file via the links below)
File tree — 1 file
skills/skills/qa/SKILL.md
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Test a website or deployed page for bugs, broken links, and visual issues”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
Investigate guides you through a disciplined five-phase debugging process: collect evidence, form ranked hypotheses, verify each one methodically, apply a minimal fix only after confirming root cause, then verify resolution. The workflow prevents guess-and-fix cycles by enforcing evidence gathering before hypothesis formation and a three-strike rule that forces re-collection rather than endless speculation.
Code Review executes a systematic multi-phase examination of pull requests and code diffs, starting with scope and intent identification before conducting a critical pass for logic errors, injection vulnerabilities, and resource leaks. Specialist lenses then apply targeted checks based on change type—tests, data access, auth, or UI—with each finding assigned a confidence level to guide merge decisions.
Hydra is a Lead-driven orchestration toolkit that lets you coordinate multiple agents through structured workflows. The Lead makes strategic decisions while workers report semantic outcomes (done, needs_rework, replan) via a typed result contract, enabling parallel task execution with explicit decision points and intervention capabilities.
dev-browser enables AI agents and developers to automate browser interactions through sandboxed JavaScript execution. Scripts run safely in an isolated QuickJS WASM environment without access to the host system, while maintaining persistent page state across multiple interactions. Navigate websites, extract data, and control web applications programmatically with reliable, repeatable automation.
This skill provides automated accessibility validation aligned with WCAG 2.2 standards, helping teams systematically verify compliance and meet regulatory obligations. Built for quality engineering workflows, it integrates accessibility checks into your testing pipeline to catch barriers early and ensure your applications remain accessible to all users.
This skill teaches you how to build and execute automated browser tests using Playwright, covering installation, core APIs, and testing workflows. Gain hands-on experience with cross-browser testing, element interaction, and assertion patterns to validate web application behavior reliably.