correctness-and-error-handling

MUST be used whenever fixing correctness and error handling issues in a Flows app. This skill finds AND fixes bugs, missing error states, unhandled rejections, and edge-case failures — it does not just report them. Triggers: correctness, error handling, bug fix, edge case, crash, unhandled, null, undefined, empty state, loading state, error boundary, try catch, async error, useEffect cleanup, type guard, runtime error, robustness.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

76%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.

Highly actionable, lean content with concrete searches and executable fixes for each defect class. The main gap is the absence of a verification checkpoint before reporting, which matters because the skill makes batch edits to production code.

Suggestions

Add an explicit validation checkpoint after the fix steps (e.g. run the test suite / type-check / build and only proceed if it passes) so batch edits are verified before reporting.

Insert a feedback loop in Step 1-8: re-run the original grep after each fix to confirm the targeted pattern is gone.

Move the larger code templates (ErrorFallback, the async-effect reference pattern) into a referenced file to reduce inline bulk and improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Mostly lean grep commands and copy-paste code that assume Claude's intelligence, with only minor over-explanation such as why an error boundary avoids a blank screen.	4 / 5
Actionability	Every step pairs a concrete grep search with executable, copy-paste-ready fix code covering the common cases (try/catch, .catch(), Zod safeParse, optional chaining, AbortController).	5 / 5
Workflow Clarity	Nine steps are clearly sequenced, but the skill performs batch in-place edits across the whole app with no validation checkpoint (e.g. run tests / verify build), so the destructive/batch cap at 3 applies.	3 / 5
Progressive Disclosure	Single-file skill with no bundle and well-organized numbered sections; content is appropriately placed with no nested references, just short of the top anchor because no split-out detail files exist.	4 / 5
	Total	16 / 20 Passed

Description

96%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.

A strong description that explicitly states both what the skill does and when to use it, with a comprehensive trigger-term list and third-person voice. Minor overlap risk from generic debugging terms keeps distinctiveness just below the top anchor.

Dimension	Reasoning	Score
Specificity	"finds AND fixes bugs, missing error states, unhandled rejections, and edge-case failures" lists multiple specific concrete actions with comprehensive coverage of the domain.	5 / 5
Completeness	"MUST be used whenever fixing correctness and error handling issues in a Flows app" gives the when, "finds AND fixes..." gives the what, reinforced by concrete trigger phrases.	5 / 5
Trigger Term Quality	The explicit "Triggers:" list provides comprehensive natural terms including synonyms and React-specific phrases (error boundary, useEffect cleanup, try catch, empty/loading state).	5 / 5
Distinctiveness Conflict Risk	Scoped to a Flows app with distinct React-specific triggers, but several generic terms (null, undefined, crash, runtime error, robustness) create minor overlap with general debugging skills.	4 / 5
	Total	19 / 20 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
metadata_version	'metadata.version' is missing	Warning

	Total	14 / 16 Passed

Repository: cognitedata/builder-skills
Path: skills/correctness-and-error-handling/SKILL.md
Commit: c87160a

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.