Is qa-chrome safe to install?

SaferSkills independently audited qa-chrome (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

.claude/skills/qa-chrome/SKILL.md · 1 file

.claude/skills/qa-chrome/SKILL.md2.7 KB · Markdown

name: qa-chrome

description: Visual tests and browser debugging via Chrome. Use to test web pages, verify visual rendering, debug with the console, or automate browser actions. Trigger when the user mentions "visual test", "Chrome", "browser", "browser console", "DOM", "screenshot", "GIF".

disable-model-invocation: true

argument-hint: "[url-or-page]"

Visual Tests and Chrome Debugging (pointer)

DevTools features (network inspection, profiling, accessibility tree, console replay) are canonical at the Chrome team's ChromeDevTools/chrome-devtools-mcp (Apache-2.0). Since 2026 it ships seven skills next to its MCP server: chrome-devtools, chrome-devtools-cli, a11y-debugging, debug-optimize-lcp, memory-leak-debugging, cookie-debugging, troubleshooting.

# The plugin bundles the skills and the MCP server. The marketplace follows the vendor's default
# branch: what you get is the plugin.json there ([email protected] on 2026-10-04).
/plugin marketplace add ChromeDevTools/chrome-devtools-mcp
/plugin install chrome-devtools-mcp@chrome-devtools-plugins
# MCP server only, pinned by us (the vendor's docs show @latest)
claude mcp add chrome-devtools --scope user npx [email protected]

This skill scopes to the manual-review checklist when using Claude Code's --chrome flag — what to look for, not how the API works.

Prerequisites

Claude Code launched with --chrome
"Claude in Chrome" extension v1.0.36+
Google Chrome open (not Brave/Arc/Firefox; no headless mode; WSL unsupported)

Manual-review checklist

When asked to visually validate a page or flow:

[ ] Page loads with no console error
[ ] Layout correct (no overflow, no overlap, no z-index bug)
[ ] Text readable (contrast meets WCAG AA — see wcag-audit)
[ ] Images loaded (no broken sources, lazy-load completes)
[ ] Links functional (no 404 in network panel)
[ ] Forms submittable (validation triggers on bad input)
[ ] Responsive OK across mobile/tablet/desktop breakpoints — see qa-design (responsive category)
[ ] No network error (no 4xx/5xx unless intentional)

Expected output

Structured report:

Screenshots/GIFs of issues
List of console + network errors with source location
Recommendations sorted by severity
Overall verdict: OK / Warnings / Errors

qa-chrome— agent skill

Is qa-chrome safe to install?

Visual Tests and Chrome Debugging (pointer)

Prerequisites

Manual-review checklist

Expected output

See also

Audit the pieces. Scan the whole. Decide.