Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
Version History
v1.0.3: Fix registry metadata — removed unsupported nested objects causing [object Object], moved env/permissions docs to body, clarified read permission is Level 3 only
What This Skill Does
QA Patrol runs automated browser tests against web applications, covering smoke checks, auth flows, payment flows, static code analysis, and data integrity comparisons. It catches cross-platform issues, auth state bugs, and integration failures that unit tests miss. All tests run on the local machine with no data sent to external servers.
It runs entirely on the local machine without sending app data, credentials, or test results to any external service, unlike cloud-based QA platforms.
When to use it
- Testing login and logout flows on a staging app before shipping
- Checking Stripe checkout pages for console errors and redirect failures
- Verifying Supabase session persistence after a page refresh
- Scanning source code for hardcoded API keys or exposed secrets
- Comparing database query results to what the UI actually displays
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: Run smoke tests on my app at https://myapp.com
- 1Navigates to https://myapp.com and captures a DOM snapshot
- 2Checks for console errors and failed network requests on the homepage
- 3Navigates through main routes and asserts expected elements exist
- 4Calculates a confidence score based on pass/fail results
- 5Outputs a structured QA report with failures, severity ratings, and recommendations
QA report showing 5 smoke tests passed, 0 failed, confidence 75%, no critical issues found