handling-api-errors

Implement standardized error handling with proper HTTP status codes and error responses. Use when implementing standardized error handling. Trigger with phrases like "add error handling", "standardize errors", or "implement error responses".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

57%

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

The content is well-structured with a clear sequenced workflow and good progressive disclosure to real reference files. It is limited by prose-described code and end-only validation rather than interleaved checkpoints.

Suggestions

Replace the prose Express handler description with an executable code block (or a minimal copy-paste snippet) to lift actionability to 3.

Interleave validation checkpoints into the workflow (e.g., verify the middleware catches a thrown error before moving to monitoring integration) rather than deferring all verification to step 9.

Trim the Prerequisites section to only non-obvious requirements to improve conciseness.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete steps, but the Overview restates capabilities and the Prerequisites section includes some expendable guidance (e.g., listing the RFC 7807 spec "for response format guidance"); could be tightened.	2 / 3
Actionability	Concrete specifics appear (typed error classes with status codes, RFC 7807 field names), but the Express error handler is described in prose rather than as an executable code block, leaving key implementation detail to the references.	2 / 3
Workflow Clarity	A clear 9-step sequence with a final test/verification step (step 9) and an error-recovery table is present, but validation checkpoints are only at the end rather than interleaved through the risky steps.	2 / 3
Progressive Disclosure	The body is an overview that signals one-level-deep references to real bundle files (implementation.md, errors.md, examples.md) with clear navigation; no nested-reference chains.	3 / 3
	Total	9 / 12 Passed

Description

82%

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 clearly answers what the skill does and when to use it, with natural trigger phrases. It is somewhat held back by generic triggers and a lack of multiple enumerated concrete actions.

Suggestions

List more concrete capabilities in the description (e.g., "map exceptions to RFC 7807 Problem Details, define typed error classes, configure environment-aware stack trace exposure") to reach specificity 3.

Sharpen triggers with more domain-specific phrasing (e.g., "RFC 7807 problem details", "centralized error middleware") to reduce overlap with generic error-handling skills.

Dimension	Reasoning	Score
Specificity	Names the domain and some actions ("proper HTTP status codes and error responses") but does not enumerate multiple concrete actions like the score-3 anchor; not vague enough for 1.	2 / 3
Completeness	Explicitly states what it does and when to use it via a "Use when implementing standardized error handling" clause plus trigger phrases, satisfying both what and when.	3 / 3
Trigger Term Quality	Provides natural trigger phrases users would say ("add error handling", "standardize errors", "implement error responses"), matching the good coverage anchor.	3 / 3
Distinctiveness Conflict Risk	The error-handling niche is somewhat specific via HTTP status codes, but "standardize errors"/"add error handling" triggers are generic enough to overlap with broader skills; not a clearly unique niche.	2 / 3
	Total	10 / 12 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 2cafb23

Reviewed: about 7 hours 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.