CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

sentry-nextjs-sdk

Full Sentry SDK setup for Next.js. Use when asked to "add Sentry to Next.js", "install @sentry/nextjs", or configure error monitoring, tracing, session replay, logging, profiling, AI monitoring, or crons for Next.js applications. Supports Next.js 13+ with App Router and Pages Router.

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a highly actionable, well-structured skill: complete executable code for every runtime and router, a clear phased workflow with verification and troubleshooting, and exemplary progressive disclosure into real one-level-deep reference files. Its only real weakness is token efficiency — several sections restate content already presented (Phase 2 list vs. table, duplicated withSentryConfig snippet, repeated backend-detection commands between Phases 1 and 4).

Suggestions

Collapse Phase 2's bullet list and 'Recommendation logic' table into a single table — they state the same feature/condition pairs twice.

Replace the repeated withSentryConfig snippet in the Source Maps section with a pointer to the options already shown (e.g. 'reuse the authToken/widenClientFileUpload options from the next.config section above'), keeping only the genuinely new token-guidance prose.

Drop the backend-detection commands from Phase 1 and defer them entirely to Phase 4 Cross-Link (or vice versa) — ../backend, go.mod, requirements.txt, and Gemfile checks currently run twice.

DimensionReasoningScore

Conciseness

The body is mostly dense, useful tables and executable code, but it contains several genuinely redundant blocks: Phase 2 presents the recommendation logic twice (a bullet list followed by a table restating the same conditions), the Source Maps section repeats the withSentryConfig snippet already shown in full, and Phase 4 re-runs the same backend-detection commands (../backend, go.mod, requirements.txt, Gemfile) from Phase 1. This exceeds 'minor instances that could be trimmed' (4) but is far from the padded concept-explanation of anchor 2.

3 / 5

Actionability

Everything is copy-paste ready: complete Sentry.init configs for all three runtimes, global-error.tsx and _error.tsx for both routers, withSentryConfig wrapping, middleware matcher exclusion, concrete detection commands, a test-error verification snippet, and a troubleshooting table with specific fixes. This fully matches the 'specific examples cover the common cases' anchor.

5 / 5

Workflow Clarity

The skill is explicitly sequenced (Phase 1 Detect → Phase 2 Recommend → Phase 3 Guide → Phase 4 Cross-Link) with a dedicated Verification section containing a checklist covering all three runtimes plus source maps and replay, and a troubleshooting table that serves as an error-recovery feedback loop. Not 4: checkpoints are explicit and checklist-form rather than merely present.

5 / 5

Progressive Disclosure

The core setup lives inline while all eight feature guides are split into references/ files that all exist on disk, are one level deep (verified: no nested .md pointers inside them), and are surfaced through a load-when table. The one external dependency (sentry-source-maps skill) is honestly flagged as not bundled with a docs fallback, keeping navigation unambiguous.

5 / 5

Total

18

/

20

Passed

Description

100%Weight 40%Scale 1-5

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 is an exemplar of the form: a clear third-person statement of what the skill does, an explicit 'Use when' clause with verbatim user phrasings including the package name, and a precise scope statement (Next.js 13+, both routers). It mirrors the rubric's good-example structure with no padding or over-claims.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete actions — "Full Sentry SDK setup for Next.js" and "configure error monitoring, tracing, session replay, logging, profiling, AI monitoring, or crons" — covering the SDK's complete feature surface. This matches the anchor for comprehensive coverage of specific concrete actions, with no minor gaps that would place it at 4.

5 / 5

Completeness

Both what ("Full Sentry SDK setup for Next.js... configure [seven product areas]. Supports Next.js 13+ with App Router and Pages Router") and when ("Use when asked to 'add Sentry to Next.js', 'install @sentry/nextjs', or configure...") are explicitly stated with concrete trigger phrases — structurally identical to the anchor-5 example. Not 4, because the 'when' clause is fully explicit rather than merely present.

5 / 5

Trigger Term Quality

It captures the exact natural phrases users would say ("add Sentry to Next.js", "install @sentry/nextjs") plus product-level synonyms (error monitoring, tracing, session replay, logging, profiling, AI monitoring, crons) and router names (App Router, Pages Router). Coverage including the package name matches the comprehensive-synonyms anchor at 5 rather than the 'a few natural terms missing' anchor at 4.

5 / 5

Distinctiveness Conflict Risk

The niche is precisely Sentry-for-Next.js, and every trigger phrase ("add Sentry to Next.js", "@sentry/nextjs", App Router/Pages Router) is scoped to it, giving minimal conflict risk even against sibling Sentry platform skills. Not 4: none of the triggers could plausibly route to a different skill.

5 / 5

Total

20

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

BigSimmo/PsychSift

Path

.claude/cloud-profile/skills/sentry-nextjs-sdk/SKILL.md

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.