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.mdSentry configuration setup
Client config file
100%
100%
Server config file
100%
100%
Edge config file
100%
100%
Correct import
100%
100%
DSN env variable
100%
100%
enableLogs flag
0%
0%
Console logging integration
0%
100%
Console log levels
0%
100%
Exception capture and performance spans
Namespace import
100%
100%
captureException usage
100%
100%
Error re-thrown
0%
0%
startSpan for API call
100%
100%
http.client op string
100%
100%
Span name includes method and path
0%
100%
startSpan for UI action
100%
100%
ui.click op string
0%
100%
span.setAttribute called
80%
100%
No bare console.error for exceptions
100%
100%
Structured logging with Sentry
Namespace import
57%
100%
Destructure logger
0%
100%
logger methods used
100%
100%
logger.fmt for interpolation
0%
100%
Plain string for static messages
100%
100%
Metadata second argument
100%
100%
Contextual metadata keys
100%
100%
No bare console.log
100%
100%
1a9819e
Table of Contents
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.