error-tracking
Set up comprehensive error tracking with Sentry to automatically capture, report, and analyze exceptions, performance issues, and application stability.
Works with
2
total installs
2
this week
162
GitHub stars
0
upvotes
Install Skill
Run in your terminal
2
installs
2
this week
162
stars
Installation Guide
How to use error-tracking on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your machine
- ›Node.js 16+ with npm — verify with
node --version - ›Active project directory where you want to add
error-tracking
Run the install command
Execute the skills CLI command in your project's root directory to begin installation:
Fetches error-tracking from aj-geddes/useful-ai-prompts and configures it for Cursor.
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate error-tracking. Access via /error-tracking 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.
Documentation
Error Tracking
Table of Contents
Overview
Set up comprehensive error tracking with Sentry to automatically capture, report, and analyze exceptions, performance issues, and application stability.
When to Use
- Production error monitoring
- Automatic exception capture
- Release tracking
- Performance issue detection
- User impact analysis
Quick Start
Minimal working example:
npm install -g @sentry/cli
npm install @sentry/node @sentry/tracing
sentry init -d
Reference Guides
Detailed implementations in the references/ directory:
| Guide | Contents |
|---|---|
| Sentry Setup | Sentry Setup, Node.js Sentry Integration |
| Express Middleware Integration | Express Middleware Integration |
| Python Sentry Integration | Python Sentry Integration |
| Source Maps and Release Management | Source Maps and Release Management, CI/CD Release Creation |
| Custom Error Context | Custom Error Context |
| Performance Monitoring | Performance Monitoring |
Best Practices
✅ DO
- Set up source maps for production
- Configure appropriate sample rates
- Track releases and deployments
- Filter sensitive information
- Add meaningful context to errors
- Use breadcrumbs for debugging
- Set user information
- Review error patterns regularly
❌ DON'T
- Send 100% of errors in production
- Include passwords in context
- Ignore configuration for environment
- Skip source map uploads
- Log personally identifiable information
- Use without proper filtering
- Disable tracking in production
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases
User Story & Requirements Generation
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
Competitive Analysis
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
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
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
Implementation Guide
Prerequisites
- ›Claude Desktop or compatible AI client
- ›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
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Related Skills
grill-me
386mattpocock/skills
premortem
197parcadei/continuous-claude-v3
deslop
118cursor/plugins
framer-motion
98pproenca/dot-skills
write-a-prd
91mattpocock/skills
travel-planner
90ailabs-393/ai-labs-claude-skills
Reviews
- AAmelia Rao★★★★★Dec 28, 2024
Keeps context tight: error-tracking is the kind of skill you can hand to a new teammate without a long onboarding doc.
- IIra Nasser★★★★★Dec 12, 2024
error-tracking fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- IIsabella Robinson★★★★★Dec 12, 2024
Registry listing for error-tracking matched our evaluation — installs cleanly and behaves as described in the markdown.
- ZZaid Thompson★★★★★Dec 4, 2024
We added error-tracking from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- JJames Sethi★★★★★Nov 23, 2024
Solid pick for teams standardizing on skills: error-tracking is focused, and the summary matches what you get after install.
- MMin Ramirez★★★★★Nov 11, 2024
Keeps context tight: error-tracking is the kind of skill you can hand to a new teammate without a long onboarding doc.
- NNoor Patel★★★★★Nov 7, 2024
error-tracking is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- HHassan Reddy★★★★★Nov 3, 2024
error-tracking has been reliable in day-to-day use. Documentation quality is above average for community skills.
- NNeel Torres★★★★★Nov 3, 2024
Useful defaults in error-tracking — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- NNoor Shah★★★★★Oct 26, 2024
Keeps context tight: error-tracking is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 55
Discussion
Comments — not star reviews- No comments yet — start the thread.