qa-chrome — independently scanned and version-tracked by SaferSkills.
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.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
DevTools features (network inspection, profiling, accessibility tree, console replay) are canonical at the Chrome team's MCP server:
.mcp.json to give Claude Code direct programmatic access during a session.This skill scopes to the manual-review checklist when using Claude Code's --chrome flag — what to look for, not how the API works.
--chromeWhen asked to visually validate a page or flow:
wcag-audit)qa-design (responsive category)Structured report:
OK / Warnings / Errorschrome-devtools-mcp (vendor MCP server, programmatic layer) — docs/recipes/recommended-vendor-skills.mdqa-design skill — UI/UX heuristics + responsive/breakpoint testing complementwcag-audit — accessibility gate when contrast/readability issues surfacespecs/marketplace-audit/qa-skills-pilot-2026-05-06.md~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.