Fetches debugging-strategies from wshobson/agents and configures it for Cursor.
3
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4
Verify installation
Confirm successful installation by checking the skill directory location:
.cursor/skills/debugging-strategies
Restart Cursor to activate debugging-strategies. Access via /debugging-strategies in your agent's command palette.
⚠
Security Notice
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.
Transform debugging from frustrating guesswork into systematic problem-solving with proven strategies, powerful tools, and methodical approaches.
When to Use This Skill
Tracking down elusive bugs
Investigating performance issues
Understanding unfamiliar codebases
Debugging production issues
Analyzing crash dumps and stack traces
Profiling application performance
Investigating memory leaks
Debugging distributed systems
Core Principles
1. The Scientific Method
1. Observe: What's the actual behavior?
2. Hypothesize: What could be causing it?
3. Experiment: Test your hypothesis
4. Analyze: Did it prove/disprove your theory?
5. Repeat: Until you find the root cause
2. Debugging Mindset
Don't Assume:
"It can't be X" - Yes it can
"I didn't change Y" - Check anyway
"It works on my machine" - Find out why
Do:
Reproduce consistently
Isolate the problem
Keep detailed notes
Question everything
Take breaks when stuck
3. Rubber Duck Debugging
Explain your code and problem out loud (to a rubber duck, colleague, or yourself). Often reveals the issue.
Systematic Debugging Process
Phase 1: Reproduce
## Reproduction Checklist1.**Can you reproduce it?**- Always? Sometimes? Randomly?
- Specific conditions needed?
- Can others reproduce it?
2.**Create minimal reproduction**- Simplify to smallest example
- Remove unrelated code
- Isolate the problem
3.**Document steps**- Write down exact steps
- Note environment details
- Capture error messages
Phase 2: Gather Information
## Information Collection1.**Error Messages**- Full stack trace
- Error codes
- Console/log output
2.**Environment**- OS version
- Language/runtime version
- Dependencies versions
- Environment variables
3.**Recent Changes**- Git history
- Deployment timeline
- Configuration changes
4.**Scope**- Affects all users or specific ones?
- All browsers or specific ones?
- Production only or also dev?
Phase 3: Form Hypothesis
## Hypothesis FormationBased on gathered info, ask:
1.**What changed?**- Recent code changes
- Dependency updates
- Infrastructure changes
2.**What's different?**- Working vs broken environment
- Working vs broken user
- Before vs after
3.**Where could this fail?**- Input validation
- Business logic
- Data layer
- External services
Phase 4: Test & Verify
## Testing Strategies1.**Binary Search**- Comment out half the code
- Narrow down problematic section
- Repeat until found
2.**Add Logging**- Strategic console.log/print
- Track variable values
- Trace execution flow
3.**Isolate Components**- Test each piece separately
- Mock dependencies
- Remove complexity
4.**Compare Working vs Broken**- Diff configurations
- Diff environments
- Diff data
Debugging Tools
JavaScript/TypeScript Debugging
// Chrome DevTools DebuggerfunctionprocessOrder(order: Order){debugger;// Execution pauses hereconst total =calculateTotal(order);console.log("Total:", total);// Conditional breakpointif(order.items.length >10){debugger;// Only breaks if condition true}return total;}// Console debugging techniquesconsole.log("Value:", value);// Basicconsole.table(arrayOfObjects);// Table formatconsole.time("operation");/* code */console.timeEnd("operation");// Timingconsole.trace();// Stack traceconsole.assert(value >0,"Value must be positive");// Assertion// Performance profilingperformance.mark("start-operation");// ... operation codeperformance.mark("end-operation");performance.measure("operation","start-operation","end-operation");console.log(performance.getEntriesByType("measure"));
›Access to product documentation and roadmap tools (Jira, Notion, etc.)
›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Steps
1Install product management skill
2Start with user story generation for known feature
3Progress to competitive analysis: research 2-3 competitors
4Use for roadmap prioritization: apply RICE/ICE scoring
5Draft stakeholder communications and refine based on feedback
6Build template library for recurring PM tasks
7Share effective prompts with product team
Common Pitfalls
⚠Not validating competitive research—verify facts before sharing
⚠Accepting user stories without involving engineering team
⚠Over-relying on frameworks without qualitative judgment
⚠Not customizing outputs to company culture and communication style
⚠Skipping stakeholder validation of generated requirements
Best Practices
✓ Do
+Validate research and competitive analysis with real data
+Collaborate with engineering when generating technical requirements
+Customize frameworks and templates to your company context
+Use skill for first drafts, refine with stakeholder input
+Document successful prompt patterns for PM tasks
+Combine AI efficiency with human judgment and intuition
✗ Don't
−Don't publish competitive analysis without fact-checking
−Don't finalize user stories without engineering review
−Don't make prioritization decisions solely on AI scoring
−Don't skip customer validation of generated requirements
−Don't ignore company-specific context and culture
💡 Pro Tips
★Provide context: company goals, constraints, customer feedback
★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
★Use skill for 70% generation + 30% customization to company needs
When to Use This
✓ 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.
Learning Path
1Basic: user stories, feature specs, status updates
