tessl-labs/aspnet-error-handling
Error handling for ASP.NET Core APIs — exception middleware, ProblemDetails,
94
90%
Does it follow best practices?
Impact
100%
1.13xAverage score across 5 eval scenarios
Passed
No known issues
Quality
Discovery
100%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 an excellent skill description that hits all the marks. It provides specific technical capabilities (ProblemDetails, IExceptionHandler, RFC 7807), uses natural developer language for triggers (raw 500 responses, stack traces leak), and explicitly states both what it does and when to use it. The description is concise yet comprehensive, making it easy for Claude to select this skill when appropriate.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and concepts: 'global exception handling, ProblemDetails (RFC 7807), IExceptionHandler, structured logging, and safe error responses' - these are all concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Error handling for ASP.NET Core APIs — global exception handling, ProblemDetails...') AND when ('Use when building or reviewing ASP.NET Core web APIs, when you see raw 500 responses, when error formats are inconsistent, or when stack traces leak to clients'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'ASP.NET Core APIs', 'web APIs', 'raw 500 responses', 'error formats', 'stack traces leak', 'error handling' - these match real developer language and problem descriptions. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: specifically targets ASP.NET Core API error handling with unique triggers like 'ProblemDetails', 'RFC 7807', 'IExceptionHandler', '500 responses', and 'stack traces leak' - unlikely to conflict with general coding or other framework skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, highly actionable skill with excellent executable code examples and clear workflow guidance. The main weakness is verbosity—the RIGHT/WRONG pattern adds value but also bulk, and some explanatory text could be trimmed. The checklist provides good validation, though the document length suggests some content could be split into reference files.
Suggestions
Trim explanatory phrases like 'This is the standard format for HTTP API errors' that explain concepts Claude already knows
Consider moving the detailed WRONG examples to a separate anti-patterns reference file, keeping only the RIGHT patterns inline
Add a brief 'Quick start' section at the top with minimal code to get exception handling working, before diving into full implementation details
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good code examples, but includes some unnecessary explanation (e.g., 'This is the standard format for HTTP API errors and is natively supported by ASP.NET Core') and the WRONG examples, while useful, add significant length. The content could be tightened. | 2 / 3 |
Actionability | Excellent actionability with fully executable, copy-paste ready code examples for every pattern. Custom exception classes, IExceptionHandler implementation, middleware alternative, and controller usage are all complete and runnable. | 3 / 3 |
Workflow Clarity | Clear sequencing with explicit registration order ('Exception handler FIRST in pipeline'), numbered sections for different components, and a comprehensive checklist at the end that serves as validation. The workflow from exception types → handler → registration → controller usage is logical and complete. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but it's a monolithic document (~300 lines) that could benefit from splitting detailed code examples into separate reference files. The verifier reference at the end is good, but inline API reference content could be externalized. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
Reviewed
Table of Contents