Token integration and implementation analyzer based on Trail of Bits' token integration checklist. Analyzes token implementations for ERC20/ERC721 conformity, checks for 20+ weird token patterns, assesses contract composition and owner privileges, performs on-chain scarcity analysis, and evaluates how protocols handle non-standard tokens. Context-aware for both token implementations and token integrations.
chrome-mcp-troubleshooting
chrome-mcp-troubleshooting is an open-source integrations skill for Claude Code and compatible agents, published by trailofbits. Its author describes it as: “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.”. The project has 6.6k stars on GitHub and is available under the CC-BY-SA-4.0 license. Add it to your setup with `/plugin marketplace add trailofbits/skills`.
What chrome-mcp-troubleshooting does
Use this skill when Claude in Chrome MCP tools fail to connect or work unreliably.
Installation
Add chrome-mcp-troubleshooting to your agent with:
/plugin marketplace add trailofbits/skillsAlways review a skill's source before installing it. This command comes from the skill's public repository; the linked repo is the source of truth for exact setup steps.
What's inside
The SKILL.md for chrome-mcp-troubleshooting is organised into these sections:
- 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
- Toggle Script
- Quick Diagnosis
- Critical Insight
- Full Reset Procedure (Claude Code CLI)
- Other Common Causes
- Multiple Chrome Profiles
When to use it
Reach for chrome-mcp-troubleshooting when you want integrations help from your agent without writing the same instructions every session. Load the skill and the agent picks it up automatically for relevant tasks.
Strengths
- Clear CC-BY-SA-4.0 license — safe to read and adapt
- Ships in trailofbits/skills, an established project with 6,646 GitHub stars
- Actively maintained (recent commits)
Topics
Frequently asked questions
- What does chrome-mcp-troubleshooting do?
- 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.
- How do I install chrome-mcp-troubleshooting?
- Run /plugin marketplace add trailofbits/skills in your agent, then reload your skills. Review the source at https://github.com/trailofbits/skills before installing.
- Is chrome-mcp-troubleshooting free to use?
- Yes. chrome-mcp-troubleshooting is free and open source under the CC-BY-SA-4.0 license, so you can read, run, and adapt it within that license's terms.
- Where does chrome-mcp-troubleshooting come from?
- chrome-mcp-troubleshooting ships inside trailofbits/skills, a repository that contains 41 catalogued skills in total. The repository's 6,646 GitHub stars apply to that whole collection, not to this skill on its own.
Related skills
More Integrations →Triages a repository's open GitHub issues and pull requests via the gh CLI. Optionally reviews and merges ready PRs — incrementally merging passing automated/bot PRs and maintainer-approved ones, and spawning review subagents for never-reviewed ones — then closes already-resolved issues with comments citing the resolving PR or commit, cross-links issues with their pending fix PRs, and assigns local-only priority and change-size estimates for everything outstanding. Use when triaging, grooming, or reviewing a repository's open issues and PRs.
Add a DeepChat LLM provider through explicit reviewed source changes. Use when a developer asks Codex to add a provider, provider profile, upstream provider config, model catalog mapping, provider auth behavior, or a special provider adapter in this repository.
Drive native desktop apps through DeepChat's built-in Computer Use tools. Use when the user asks to operate, inspect, automate, or perform a GUI task in a real desktop application.
Drive a native macOS app via the cua-driver MCP server or CLI — snapshot its AX tree, click/type/scroll by element_index, verify via re-snapshot. Use when the user asks you to operate, drive, automate, or perform a GUI task in a real macOS application on the host (e.g. "open a file in TextEdit", "navigate to /Applications in Finder", "click the Save button in Numbers").