Uses Chrome DevTools MCP for accessibility (a11y) debugging and auditing based on web.dev guidelines. Use when testing semantic HTML, ARIA labels, focus states, keyboard navigation, tap targets, and color contrast.
Data sourced from ClawHub. View on ClawSkills
Select your agent
Option 1: Install via CLI (recommended)
Recommended (no pre-install needed)
npx clawhub@latest --dir ~/.claude/skills install troubleshootingOr via clawhub CLI (if already installed)
clawhub --dir ~/.claude/skills install troubleshootingβ οΈ Requires Node.js 18+. No Node? Use Option 2 below to download the ZIP instead. Install Node.js β
Option 2: Manual install (no Node required)
Download the ZIP, extract it, and place the folder at the path below. Restart your agent to activate.
Install path
~/.claude/skills/troubleshooting/π‘Extract and place the folder at the path above, then restart your agent.
What troubleshooting can do for your AI workflow
Uses chrome devtools mcp directly from your Claude conversation
Native Claude integration via the open Model Context Protocol (MCP)
One-command installation β no complex setup required
Combine with other skills to build powerful multi-step AI workflows
Try these prompts with your AI agent after installing troubleshooting
Help me get started with troubleshooting
Explains what troubleshooting does, walks through the setup, and runs a quick demo based on your current project
Use troubleshooting to uses Chrome DevTools MCP for accessibility (a11y) debugging and aud...
Invokes troubleshooting with the right parameters and returns the result directly in the conversation
What can I do with troubleshooting in my ai agent workflow?
Lists the top use cases for troubleshooting, with example commands for each scenario
Guides & tutorials for AI skills
The 7 AI Skills Every Software Developer Should Have Installed in 2026
After testing dozens of developer-focused AI skills, these are the seven that have proven genuinely useful across different tech stacks and workflows β not just impressive demos, but tools that hold up under daily use.
MCP Skills vs Native Claude Tools: What's the Difference and When to Use Each
Claude comes with built-in capabilities, but MCP skills extend it in ways the base model can't. Here's a clear breakdown of what each type of tool is good for, with real examples of when to reach for a skill versus relying on Claude's native abilities.
troubleshooting extends your AI assistant with the ability to uses Chrome DevTools MCP for accessibility (a11y) debugging and auditing based on web.dev guidelines. Use when testing semantic HTML, ARIA labels, focus states, keyboard navigation, tap targets, and color contrast. Rather than leaving your conversation to handle this manually, you can ask your Claude agent directly β and it will take care of the task end-to-end, using troubleshooting as its underlying capability.
troubleshooting integrates with Claude through the Model Context Protocol (MCP) standard. The skill is version-controlled and shareable β if you work with a team, you can commit the skill to your project repo and everyone gets the same capability without any extra setup.
To install troubleshooting, copy the skill folder to `~/.claude/skills/troubleshooting/` for use across all your projects, or `.claude/skills/troubleshooting/` for a single project. Restart Claude and the skill is immediately active β invoke it with `/troubleshooting` or just describe your goal and the AI will pick it up automatically.
troubleshooting is a community-contributed AI productivity skill available through DiscoverAISkills. Like all skills on DiscoverAISkills, it is free to install and use. The broader AI skills ecosystem continues to expand as developers contribute new capabilities across categories like developer tools, data analysis, writing, automation, and more.
Place the skill folder at ~/.claude/skills/troubleshooting/ for personal use (all projects), or .claude/skills/troubleshooting/ for project-specific use. Restart your AI client, then invoke with /troubleshooting or let the AI discover it automatically.
troubleshooting supports Claude. It integrates seamlessly with these AI platforms to extend their capabilities.
troubleshooting is free to install. Check the repository for licensing information.
Uses Chrome DevTools MCP for accessibility (a11y) debugging and auditing based on web.dev guidelines. Use when testing semantic HTML, ARIA labels, focus states, keyboard navigation, tap targets, and color contrast.
Troubleshooting common problems with OpenClaw plug-in installation
Troubleshooting methods and best practices for solving common npm package name errors, permission issues, and installation verification during OpenClaw plug-in installation.
Troubleshooting OpenClaw Feishu issues
Feishu plug-in troubleshooting tool. Contains FAQ and in-depth diagnostic commands (/feishu_doctor). Frequently Asked Questions are available for review at any time. Diagnostic commands are used to troubleshoot complex problems (multiple authorizations still fail, automatic authorization cannot be resolved, etc.). They check account configuration, API connectivity, application permissions, user authorization status, and generate detailed diagnostic reports and solutions.
Platforms
Automate my ai agent tasks using troubleshooting
Identifies repetitive steps in your workflow and sets up troubleshooting to handle them automatically