.claude/skills/browser-qaRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
Automate visual testing and UI interaction verification. 4-phase methodology: smoke test (console errors, network status, Web Vitals), interaction test (forms, auth, user journeys), visual regression (breakpoints, dark mode), accessibility audit (WCAG AA, keyboard nav). Trigger phrases: browser test, visual testing, UI verification, QA checklist, pre-ship testing.
These states come from the source or distribution context. None of the entries below are SkillVetAI compatibility test results.
These checks parse the fixed package against dated platform rules. They do not execute the Skill or verify task behavior.
.claude/skills/browser-qaRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
.agents/skills/browser-qaRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
skills/browser-qaRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
This command is recorded from the source ecosystem and resolves the registry's latest release. The fixed release shown on this page should be inspected before adoption.
clawhub install @djc00p/browser-qaclawhub inspect @djc00p/browser-qa --version 1.0.2This automated, non-executing scan is bound to this release hash. It is not a safety certification and may contain false positives or false negatives.
This is registry-supplied evidence for the recorded release, not an independent SkillVetAI scan. Check the canonical source for the full report, scanner versions, scope, and current moderation state.
The catalog stores hashes and an inventory summary for change detection. It does not republish the package contents.
sha256:c6d5ff79f65e59ddcd7583d0555aec16b752c38f094f4838857ecc5c98818da4_meta.jsonreferences/tools.mdreferences/wcag.mdskill-card.mdSKILL.mdAdd a Scope and Safety section: use only against sites you own or have permission to test, require a staging or sandbox URL, dedicated test accounts and test payment data, and treat form submission, account creation and checkout as actions needing explicit per-action approval.