Status: Production Ready
Works with
Last Updated: 2026-02-03
Dependencies: Chrome MCP tools (optional), debugger agent, code-reviewer agent
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiondeep-debugExecute the skills CLI command in your project's root directory to begin installation:
Fetches deep-debug from jezweb/claude-skills 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 deep-debug. Access via /deep-debug in 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
0
total installs
0
this week
695
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
695
stars
Status: Production Ready Last Updated: 2026-02-03 Dependencies: Chrome MCP tools (optional), debugger agent, code-reviewer agent
| Command | Purpose |
|---|---|
/debug |
Guided debugging workflow with evidence gathering and parallel investigation |
/debug [description of the bug]
Or invoke naturally:
For browser-related bugs, use Chrome MCP tools:
// Get network requests (look for duplicates, failures, timing)
mcp__claude-in-chrome__read_network_requests
// Get console logs (errors, warnings, debug output)
mcp__claude-in-chrome__read_console_messages
// Get page state
mcp__claude-in-chrome__read_page
For backend bugs, gather:
Launch these agents simultaneously with the gathered evidence:
Task(subagent_type="debugger", prompt="""
EVIDENCE: [paste network/console evidence]
Trace the execution path that leads to this bug. Find:
1. Where the bug originates
2. What triggers it
3. The exact line/function causing the issue
Focus on TRACING, not guessing.
""")
Task(subagent_type="code-reviewer", prompt="""
EVIDENCE: [paste evidence]
Review the relevant code for common bug patterns:
- React useCallback/useMemo dependency issues
- Stale closures
- Race conditions
- State update ordering
- Missing error handling
Find patterns that EXPLAIN the evidence.
""")
Task(subagent_type="Explore", prompt="""
EVIDENCE: [paste evidence]
Map all entry points that could trigger this behavior:
- All places [function] is called
- All event handlers involved
- All state updates that affect this
Find if something is being called MULTIPLE TIMES or from UNEXPECTED places.
""")
After agents complete, look for:
| Signal | Meaning |
|---|---|
| All 3 agree on root cause | High confidence - fix it |
| 2 agree, 1 different | Investigate the difference |
| All 3 different | Need more evidence |
After implementing the fix, re-gather the same evidence to confirm:
Network tab showed 2 fetch requests for the same message.
| Agent | Finding |
|---|---|
| debugger | state.messages in useCallback deps causes callback recreation |
| code-reviewer | Same finding + explained React pattern causing it |
| Explore | Verified UI layer wasn't double-calling (ruled out) |
sendMessage useCallback had state.messages in dependency array. Every state update recreated the callback, causing duplicate calls during React re-renders.
Use stateRef to access current state without including in dependencies:
const stateRef = useRef(state);
stateRef.current = state;
const sendMessage = useCallback(async (text) => {
// Use stateRef.current instead of state
const messages = stateRef.current.messages;
// ...
}, [/* state.messages removed */]);
state in useCallback dependencies causing recreation| Tool | Use For |
|---|---|
read_network_requests |
See all fetch/XHR calls, duplicates, failures |
read_console_messages |
Errors, warnings, debug logs |
read_page |
Current DOM state |
javascript_tool |
Execute debug code in page context |
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.
jezweb/claude-skills
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
deep-debug reduced setup friction for our internal harness; good balance of opinion and flexibility.
deep-debug is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: deep-debug is the kind of skill you can hand to a new teammate without a long onboarding doc.
We added deep-debug from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
We added deep-debug from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: deep-debug is the kind of skill you can hand to a new teammate without a long onboarding doc.
Useful defaults in deep-debug — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
deep-debug has been reliable in day-to-day use. Documentation quality is above average for community skills.
deep-debug fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for deep-debug matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 29