Skip to content
Agentmart
Submit a tool

api-error-handling

Design API error responses.

Skill by 0xzahed

IndexedMIT
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/0xzahed-api-error-handling

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Design API error responses. Use when defining and implementing API errors.

Use cases: design, backend

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/api-error-handling

What's inside

Skill name
api-error-handling
Description
Design API error responses. Use when defining and implementing API errors.
License
MIT
Metadata
tags: api, error, handling
Instructions
28 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# API Error Handling

## Use this skill when
- Defining a standard error contract
- Returning precise error codes and messages
- Adding error context without leaking internals

## Do not use this skill when
- Internal error logging (use backend-error-handling)

## Instructions
1. Return a structured error body: code, message, details/fields, traceId.
2. Include a stable, machine-readable error code per failure kind.
3. Provide field-level validation errors; mention constraints in the message.
4. Use 4xx for client errors and 5xx for server errors; never 200 for failures.
5. Correlate errors with request tracing.
6. Do not leak stack traces, SQL, or internal paths.
7. Document the error taxonomy in the API spec.

## Output Format
- Error schema | code taxonomy | per-endpoint error matrix

## Common Mistakes
- 200 with an error payload
- Free-text messages only
- Exposing stack traces to clients

From 0xzahed/antigravity-skills, MIT.

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
Sep 16, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from 0xzahed

Cite this page

api-error-handling skill. Agent Mart. https://agentmart.dev/skills/0xzahed-api-error-handling (last updated 2026-10-24)