claude in chrome troubleshooting

Name: claude in chrome troubleshooting
Author: trailofbits

by trailofbits·18d ago

Diagnose and fix Claude in Chrome MCP extension connectivity issues. Use when mcp__claude-in-chrome__* tools fail, retu…

Claude CodeMedium risk · 中风险open source · 开源

Editor's verdict· 编辑结论

Diagnose and fix Claude in Chrome MCP extension connectivity issues. Use when mcp__claude-in-chrome__* tools fail, return "Browser extension is not connected", or behave erratically.
— Editorial team · 编辑团队

Install via Skills CLI

Use npx skills add to install this skill into the selected agent. Phase 0 commands are generated from source rules, not verified.

Codex

npx skills add https://github.com/trailofbits/skills/blob/main/plugins/claude-in-chrome-troubleshooting/skills/claude-in-chrome-troubleshooting/SKILL.md -g -a codex -y

Drop `-g` to install project-locally

✓

Best for适合什么场景

网页自动化
页面测试
浏览器操作

✗

Not for不适合什么场景

Workflows that require stronger human review than this catalog entry documents.需要比当前目录条目更严格人工复核的工作流。

vs alternativesvs 其他选择

Full compare table完整对比表 →

#1QA Loop

Open the product, try the flow, fix what breaks, repeat.

★ 4.9·15k stars

diff · 差异Best browser QA pick when you need evidence to leave a paper trail. Each run produces screenshots, console diffs, and a reproducible action log — much harder for stakeholders to wave off than "I tested it locally." Works well as a pre-merge gate and for filing bugs with repro steps attached. Not for unit tests, and not for authenticated production sessions where the screenshot itself becomes a data risk.

#2GStack QA

Open the app, test the flow, fix what breaks.

★ 4.8·80k stars

diff · 差异Best when browser QA needs to close the loop — find the bug, propose the fix, verify the fix, leave evidence. Where qa-loop emphasizes evidence trails for stakeholder reporting, gstack-qa emphasizes shipping the fix in the same session. Strongest on frontend refactors and visual regressions. Same screenshot data-risk caveat as qa-loop: don't point it at authenticated production sessions where the screenshot itself becomes a leak.

#3Canary Watch

Verify the live deploy before users tell you it is broken.

★ 4.6·8.2k stars

diff · 差异Best for the 10–30 minutes right after a deploy hits production, when "we already verified in staging" starts to wear thin. Hits a curated list of critical routes, watches for console errors, broken pages, and visual diffs against baseline. Lightweight by design — it is not a synthetic monitoring platform. Pair with release-briefing for the comms side. Don't use it as a substitute for pre-merge QA; that's qa-loop or gstack-qa's job.

Side-by-side compare维度对比

Key differences with same-lane alternatives

	this skill · 当前claude in chrome troubleshooting	QA Loop	GStack QA	Canary Watch
Rating · 评分	—	4.9	4.8	4.6
Stars · 星标	5.1k	15k	80k	8.2k
Risk · 风险	Medium risk · 中风险	Medium risk · 中风险	Medium risk · 中风险	Medium risk · 中风险
Best for · 最适合	网页自动化	Browser smoke tests	Open the app, test the flow, fix what breaks.	Verify the live deploy before users tell you it is broken.
Not for · 不适合	Workflows that require stronger human review than this catalog entry documents.	Pure unit testing	Workflows that require stronger human review than this catalog entry documents.	Workflows that require stronger human review than this catalog entry documents.

Audit notes审计备注

last reviewed 2026-06-03 · 复查

Source源码open on GitHub · 公开✓

Author作者community · 社区!

Network网络访问network access · 需联网✓

Filesystem文件写入writes to repo · 写入仓库!

Dependencies依赖many deps · 依赖较多✓

Telemetry遥测none · 无✓