claude-in-chrome-troubleshooting
No security findings. Scanned 1 time, most recently 2026-02-06.
Second scanner: NVIDIA SkillSpector
The two scanners disagree: Cisco found nothing and SkillSpector says do not install. One of them has a blind spot here; read the skill before trusting either. How the two scanners compare across the whole corpus: Two scanners, one corpus.
What this skill does
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.
- Package
- 1 file, 10 KB
- SKILL.md
- 1158 words, 12+ sections
- Code
- None. Instructions only.
SKILL.md covers: Claude in Chrome MCP Troubleshooting · When to Use · When NOT to Use · The Claude.app vs Claude Code Conflict (Primary Issue) · Two Native Hosts, Two Socket Formats · Why They Conflict · The Fix: Disable Claude.app's Native Host · Disable the Claude.app native messaging config · Ensure the Claude Code config exists and points to the wrapper · Disable the Claude Code native messaging config · Toggle Script · Quick Diagnosis
Findings
No findings. SAFE
What is in the package
| File | Kind | Size |
|---|---|---|
SKILL.md | doc | 10 KB |
External hosts referenced
github.com
Hostnames that appear in the skill's files. Referencing a host is not a finding; compare against the findings above and the skill's stated purpose.
Environment variables referenced
CONFIG_DIR
Package contents recorded 2026-10-22 at commit a50696e20581. The scan above ran against the version current at scan time; the two can differ if the skill has since been updated.
What we checked
- Static analyzer. Pattern rules over SKILL.md and bundled files: known-bad commands, exfiltration URLs, secrets, obfuscation.
- Behavioral analyzer. Checks what the skill asks the agent to do against what its description claims it does.
- Llm analyzer. A language model reads the skill and reports intent-level issues the rules cannot express.
- Trigger analyzer. Looks for instructions that fire on conditions the user did not ask for.
- Meta analyzer. A second model pass that validates, deduplicates and re-scores the other analyzers' findings.
What we did not check
- Runtime behaviour. The skill was not executed; findings come from reading its files.
- Anything fetched at install or run time, including remote scripts, package dependencies, and URLs the skill tells the agent to open.
- Content the analyzers cannot read: images, binaries, and some non-English text.
- Known scanner bypass classes. See the methodology and limitations page.
Sources
- Repository: https://github.com/trailofbits/skills
- Raw scan result: plugins-claude-in-chrome-troubleshooting-skills-claude-in-chrome-troubleshooting-scan.json
- Badge for your README:
- Request a re-scan