product-factory/error-handling
Apply this skill when building error handling, error boundaries, logging, monitoring, or observability in a Next.js + TypeScript + Drizzle application. Triggers on requests like "handle errors", "add error boundary", "add logging", "add monitoring", "set up Sentry", "why is this failing silently", "add a 404 page", or any time you are building features that need to handle failure gracefully. Use proactively — every new feature should account for error states.
93
Quality
93%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description with excellent trigger term coverage and completeness. It clearly defines when to use the skill with explicit trigger phrases and proactive guidance. The main weakness is that the capabilities could be more concrete—listing specific actions like 'configure error tracking services' or 'implement custom error classes' rather than general categories.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (error handling, logging, monitoring in Next.js + TypeScript + Drizzle) and lists several actions (error boundaries, logging, monitoring, observability), but doesn't describe concrete specific actions like 'configure Sentry alerts' or 'implement try-catch patterns'. | 2 / 3 |
Completeness | Clearly answers both what (error handling, boundaries, logging, monitoring, observability in Next.js/TypeScript/Drizzle) and when (explicit 'Triggers on requests like...' clause with multiple examples, plus proactive guidance for new features). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'handle errors', 'add error boundary', 'add logging', 'add monitoring', 'set up Sentry', 'why is this failing silently', 'add a 404 page'. These are realistic phrases users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: specifically scoped to error handling/observability in a Next.js + TypeScript + Drizzle stack. The specific technology combination and focused domain (errors, logging, monitoring) make conflicts with other skills unlikely. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill with excellent actionability and conciseness. It provides comprehensive, executable patterns for error handling across the full Next.js stack without unnecessary explanation. The main weakness is that the content could be better organized with progressive disclosure—splitting detailed implementations into separate files while keeping the main skill as a navigational overview.
Suggestions
Consider splitting detailed implementations (logger, Sentry setup, API error utilities) into separate reference files and linking to them from a more concise overview
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, assuming Claude's competence with TypeScript, Next.js, and Drizzle. No unnecessary explanations of basic concepts; every section delivers actionable patterns without padding. | 3 / 3 |
Actionability | Provides fully executable, copy-paste ready code examples throughout—error boundaries, server actions with typed results, API route handlers, mutation patterns, and a complete logger implementation. Specific file paths and patterns are clearly shown. | 3 / 3 |
Workflow Clarity | Clear organization with explicit patterns for different error types. The error classification table provides decision guidance, and the file structure diagram shows exactly where error boundaries belong. The typed result pattern includes validation-then-action sequencing. | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear sections and headers, but it's a monolithic document (~200 lines) that could benefit from splitting detailed implementations (Sentry setup, logger implementation) into separate reference files while keeping the SKILL.md as an overview. | 2 / 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.
Install with Tessl CLI
npx tessl i product-factory/error-handlingReviewed
Table of Contents