sentry
Sentry error monitoring and performance tracing patterns for Next.js applications.
72
60%
Does it follow best practices?
Impact
91%
1.44xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/sentry/SKILL.mdQuality
Discovery
32%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description identifies a clear technology stack (Sentry + Next.js) but is too brief and lacks actionable detail. It fails to specify concrete actions the skill enables and critically omits any 'Use when...' guidance, making it difficult for Claude to know when to select this skill over others.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when setting up Sentry in Next.js, configuring error boundaries, debugging production errors, or implementing performance monitoring'.
List specific concrete actions such as 'Configure Sentry SDK, set up source maps, create custom error boundaries, implement performance spans, configure alert rules'.
Include additional natural trigger terms users might say: 'crash reporting', 'exception tracking', 'APM', 'observability', 'production debugging'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Sentry, Next.js) and general categories (error monitoring, performance tracing), but lacks concrete actions like 'configure alerts', 'set up source maps', or 'create custom spans'. | 2 / 3 |
Completeness | Describes what the skill covers at a high level but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Sentry', 'error monitoring', 'performance tracing', and 'Next.js', but misses common variations users might say like 'debugging', 'exceptions', 'APM', 'observability', or 'crash reporting'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'Sentry' and 'Next.js' provides some distinctiveness, but 'error monitoring' and 'performance tracing' could overlap with other observability or debugging skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill that provides concise, actionable Sentry integration patterns for Next.js. The code examples are complete and cover the main use cases effectively. The main weakness is the lack of a clear setup workflow or validation steps to confirm Sentry is properly configured and receiving events.
Suggestions
Add a brief setup workflow with validation step (e.g., 'After configuration, trigger a test error and verify it appears in Sentry dashboard within 30 seconds')
Consider adding a troubleshooting note for common issues like missing DSN or events not appearing
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing only essential information. No unnecessary explanations of what Sentry is or how error monitoring works - it jumps straight to actionable patterns. | 3 / 3 |
Actionability | Every section includes complete, executable code examples that are copy-paste ready. The code covers exception catching, performance tracing for UI and API calls, configuration, and structured logging with real-world patterns. | 3 / 3 |
Workflow Clarity | While individual patterns are clear, there's no explicit workflow for setting up Sentry in a new project or validating that instrumentation is working correctly. The configuration section lists files but doesn't sequence the setup process. | 2 / 3 |
Progressive Disclosure | For a skill of this size (~80 lines), the content is well-organized with clear section headers. Each section covers a distinct concern (exception catching, tracing, config, logging) without needing external file references. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- brianlovin/claude-config
- Commit
1a9819e
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.