How do I install the Web QA Bot skill?

Run npx get-skill add tomevault-io/web-qa-bot in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Web QA Bot safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Web QA Bot?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Web QA Bot free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Web QA Bot?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Web QA Bot by tomevault-io — Agent Skill

Name: Web QA Bot
Author: tomevault-io

File contents

web-qa-bot

AI-powered web application QA automation using accessibility-tree based testing.

Overview

This skill provides tools for automated QA testing of web applications. It uses browser accessibility trees for reliable element detection instead of fragile CSS selectors.

Installation

npm install -g web-qa-bot agent-browser
agent-browser install

Commands

Quick Smoke Test

web-qa-bot smoke https://example.com

Runs basic health checks:

Page loads successfully
No console errors
Navigation elements present
Images have alt text

Run Test Suite

web-qa-bot run ./tests/suite.yaml --output report.md

Generate PDF Report

web-qa-bot report ./results.json -o report.pdf -f pdf

Use Cases

1. Quick Site Health Check

# Smoke test a production URL
web-qa-bot smoke https://app.example.com --checks pageLoad,consoleErrors,navigation

2. Pre-deployment QA

Create a test suite and run before each deployment:

# tests/critical-paths.yaml
name: Critical Paths
baseUrl: https://staging.example.com

tests:
  - name: Login flow
    steps:
      - goto: /login
      - type: { ref: Email, text: test@example.com }
      - type: { ref: Password, text: testpass }
      - click: Sign In
      - expectVisible: Dashboard
      - expectNoErrors: true

web-qa-bot run ./tests/critical-paths.yaml --output qa-report.pdf -f pdf

3. Monitor for Regressions

# Run tests and fail CI if issues found
web-qa-bot run ./tests/smoke.yaml || exit 1

4. Programmatic Testing

import { QABot } from 'web-qa-bot'

const qa = new QABot({
  baseUrl: 'https://example.com',
  headless: true
})

await qa.goto('/')
await qa.click('Get Started')
await qa.snapshot()
qa.expectVisible('Sign Up')
await qa.close()

Integration with agent-browser

This tool wraps agent-browser CLI for browser automation:

# Connect to existing browser session
web-qa-bot smoke https://example.com --cdp 18800

# Run headed for debugging
web-qa-bot run ./tests/suite.yaml --no-headless

Test Results Format

Results are returned as structured JSON:

{
  "name": "Smoke Test",
  "url": "https://example.com",
  "summary": {
    "total": 4,
    "passed": 3,
    "failed": 0,
    "warnings": 1
  },
  "tests": [
    {
      "name": "Page Load",
      "status": "pass",
      "duration": 1234
    }
  ]
}

Tips

Use role-based selectors - More reliable than CSS classes
Check console errors - Often reveals hidden issues
Test both navigation methods - Direct URL and in-app routing
Screenshot on failure - Automatic in test suites
Monitor for modals - Can block interactions

Report Formats

Markdown - Default, human-readable
PDF - Professional reports via ai-pdf-builder
JSON - Machine-readable for CI/CD

Troubleshooting

"agent-browser not found"

npm install -g agent-browser
agent-browser install

"Element not found"

Take a snapshot first to see available refs:

agent-browser snapshot

"Timeout waiting for element"

Increase timeout or check if element is behind a loading state:

steps:
  - waitMs: 2000
  - waitFor: "Loading" # Wait for loading to appear
  - waitFor: "Content" # Then wait for content

Links

GitHub
npm

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: web-qa-botdescription: AI-powered web application QA automation using accessibility-tree based testing. Smoke tests, test suites, and PDF reports. Use when this capability is needed.---# web-qa-botAI-powered web application QA automation using accessibility-tree based testing.## OverviewThis skill provides tools for automated QA testing of web applications. It uses browser accessibility trees for reliable element detection instead of fragile CSS selectors.## Installation```bashnpm install -g web-qa-bot agent-browseragent-browser install```## Commands### Quick Smoke Test```bashweb-qa-bot smoke https://example.com```Runs basic health checks:- Page loads successfully- No console errors- Navigation elements present- Images have alt text### Run Test Suite```bashweb-qa-bot run ./tests/suite.yaml --output report.md```### Generate PDF Report```bashweb-qa-bot report ./results.json -o report.pdf -f pdf```## Use Cases### 1. Quick Site Health Check```bash# Smoke test a production URLweb-qa-bot smoke https://app.example.com --checks pageLoad,consoleErrors,navigation```### 2. Pre-deployment QACreate a test suite and run before each deployment:```yaml# tests/critical-paths.yamlname: Critical PathsbaseUrl: https://staging.example.comtests: - name: Login flow steps: - goto: /login - type: { ref: Email, text: test@example.com } - type: { ref: Password, text: testpass } - click: Sign In - expectVisible: Dashboard - expectNoErrors: true``````bashweb-qa-bot run ./tests/critical-paths.yaml --output qa-report.pdf -f pdf```### 3. Monitor for Regressions```bash# Run tests and fail CI if issues foundweb-qa-bot run ./tests/smoke.yaml || exit 1```### 4. Programmatic Testing```typescriptimport { QABot } from 'web-qa-bot'const qa = new QABot({ baseUrl: 'https://example.com', headless: true})await qa.goto('/')await qa.click('Get Started')await qa.snapshot()qa.expectVisible('Sign Up')await qa.close()```## Integration with agent-browserThis tool wraps agent-browser CLI for browser automation:```bash# Connect to existing browser sessionweb-qa-bot smoke https://example.com --cdp 18800# Run headed for debuggingweb-qa-bot run ./tests/suite.yaml --no-headless```## Test Results FormatResults are returned as structured JSON:```json{ "name": "Smoke Test", "url": "https://example.com", "summary": { "total": 4, "passed": 3, "failed": 0, "warnings": 1 }, "tests": [ { "name": "Page Load", "status": "pass", "duration": 1234 } ]}```## Tips1. **Use role-based selectors** - More reliable than CSS classes2. **Check console errors** - Often reveals hidden issues3. **Test both navigation methods** - Direct URL and in-app routing4. **Screenshot on failure** - Automatic in test suites5. **Monitor for modals** - Can block interactions## Report Formats- **Markdown** - Default, human-readable- **PDF** - Professional reports via ai-pdf-builder- **JSON** - Machine-readable for CI/CD## Troubleshooting### "agent-browser not found"```bashnpm install -g agent-browseragent-browser install```### "Element not found"Take a snapshot first to see available refs:```bashagent-browser snapshot```### "Timeout waiting for element"Increase timeout or check if element is behind a loading state:```yamlsteps: - waitMs: 2000 - waitFor: "Loading" # Wait for loading to appear - waitFor: "Content" # Then wait for content```## Links- [GitHub](https://github.com/NextFrontierBuilds/web-qa-bot)- [npm](https://www.npmjs.com/package/web-qa-bot)---> Converted and distributed by [TomeVault](https://tomevault.io/claim/demerzels-lab) — claim your Tome and manage your conversions.

Frequently asked questions

Web QA Bot