tessl-labs/frontend-error-handling
Proactive error handling for React and vanilla JS frontends — every data-fetching component gets loading, error, and empty states, error boundaries, fetch error handling, form validation, optimistic rollback
90
84%
Does it follow best practices?
Impact
100%
1.38xAverage score across 5 eval scenarios
Passed
No known issues
Quality
Discovery
85%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 that clearly articulates specific error handling patterns and when to apply them. The proactive nature ('even when the user does not ask') is well-communicated. The main weakness is trigger term coverage—it relies on technical terms rather than natural user language variations.
Suggestions
Add natural user phrases like 'web app', 'UI component', 'API calls', or 'frontend app' to improve trigger term coverage for how users naturally describe their work.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'loading, error, and empty states', 'error boundaries', 'network + HTTP + parse error handling'. Clearly describes what patterns must be applied. | 3 / 3 |
Completeness | Clearly answers both what ('loading, error, empty states', 'error boundaries', 'fetch error handling') AND when ('whenever building frontend components — even when the user does not ask for error handling'). The 'Apply these patterns automatically' serves as explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'React', 'vanilla JS', 'frontends', 'component', 'fetch', but missing common user phrases like 'UI', 'web app', 'API calls', or file extensions. Users might not say 'error handling' when they need this skill. | 2 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on error handling patterns for frontend development. The combination of 'React', 'vanilla JS', 'error boundaries', and 'fetch error handling' creates a distinct scope unlikely to conflict with general coding or backend skills. | 3 / 3 |
Total | 11 / 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 covering React and vanilla JS error handling patterns comprehensively. The four-state model and final checklist provide clear workflow guidance. However, the document is verbose for a SKILL.md overview and would benefit from splitting advanced patterns into separate files with clearer progressive disclosure.
Suggestions
Extract advanced patterns (optimistic updates, retry mechanisms, toast/notification, form validation) into separate reference files and link to them from a condensed overview
Remove explanatory prose that Claude already knows (e.g., 'A missing loading state means a blank flash') to improve token efficiency
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some explanatory text that Claude would already know (e.g., explaining what network errors, HTTP errors, and parse errors are). The content could be tightened by removing phrases like 'Never skip any of these' and reducing the explanatory prose between code blocks. | 2 / 3 |
Actionability | Excellent actionability with fully executable TypeScript/React code examples throughout. Every pattern includes copy-paste ready implementations: apiRequest wrapper, complete component patterns, error boundaries, form handling, retry mechanisms, and toast notifications. | 3 / 3 |
Workflow Clarity | Clear four-state model (loading, error, empty, success) is explicitly defined upfront. The checklist at the end provides explicit validation steps. Each pattern shows the complete flow including error recovery (retry buttons, rollback for optimistic updates). | 3 / 3 |
Progressive Disclosure | The skill is a long monolithic document (~300 lines) that could benefit from splitting advanced patterns (optimistic updates, retry mechanisms, toast patterns) into separate reference files. The verifiers section at the end references external files appropriately, but the main content lacks clear navigation to separate detailed materials. | 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