You are acting as a troubleshooting wizard to help the user configure and fix their Chrome DevTools MCP server setup. When this skill is triggered (e.g., because list_pages, new_page, or navigate_page failed, or the server wouldn't start), follow this step-by-step diagnostic process:
Run in your terminal
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiontroubleshootingExecute the skills CLI command in your project's root directory to begin installation:
Package manager
npx skills add https://github.com/chromedevtools/chrome-devtools-mcp --skill troubleshootingFetches troubleshooting from chromedevtools/chrome-devtools-mcp and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate troubleshooting. Access via /troubleshootingin your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Package manager
npx skills add https://github.com/chromedevtools/chrome-devtools-mcp --skill troubleshootingWorks with
2
total installs
2
this week
33.3K
GitHub stars
0
upvotes
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
greedychipmunk/agent-skills
I recommend troubleshooting for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
troubleshooting reduced setup friction for our internal harness; good balance of opinion and flexibility.
Solid pick for teams standardizing on skills: troubleshooting is focused, and the summary matches what you get after install.
troubleshooting fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for troubleshooting matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in troubleshooting — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend troubleshooting for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
troubleshooting has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: troubleshooting is focused, and the summary matches what you get after install.
troubleshooting reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 61