Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
AI-powered automated QA for web apps. Smoke tests, accessibility, visual regression. Works with Cursor, Claude, ChatGPT, Copilot. Vibe-coding ready.
AI-powered automated QA for web apps. Smoke tests, accessibility, visual regression. Works with Cursor, Claude, ChatGPT, Copilot. Vibe-coding ready.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
AI-powered web application QA automation using accessibility-tree based testing.
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.
npm install -g web-qa-bot agent-browser agent-browser install
web-qa-bot smoke https://example.com Runs basic health checks: Page loads successfully No console errors Navigation elements present Images have alt text
web-qa-bot run ./tests/suite.yaml --output report.md
web-qa-bot report ./results.json -o report.pdf -f pdf
# Smoke test a production URL web-qa-bot smoke https://app.example.com --checks pageLoad,consoleErrors,navigation
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
# Run tests and fail CI if issues found web-qa-bot run ./tests/smoke.yaml || exit 1
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()
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
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 } ] }
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
Markdown - Default, human-readable PDF - Professional reports via ai-pdf-builder JSON - Machine-readable for CI/CD
npm install -g agent-browser agent-browser install
Take a snapshot first to see available refs: agent-browser snapshot
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
GitHub npm
Messaging, meetings, inboxes, CRM, and teammate communication surfaces.
Largest current source with strong distribution and engagement signals.