api-error-taxonomy

Define consistent API error codes and responses. Use when a mid-level developer needs error standardization.

16 stars

Best use case

api-error-taxonomy is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Define consistent API error codes and responses. Use when a mid-level developer needs error standardization.

Teams using api-error-taxonomy should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/api-error-taxonomy/SKILL.md --create-dirs "https://raw.githubusercontent.com/diegosouzapw/awesome-omni-skill/main/skills/backend/api-error-taxonomy/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/api-error-taxonomy/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How api-error-taxonomy Compares

Feature / Agentapi-error-taxonomyStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Define consistent API error codes and responses. Use when a mid-level developer needs error standardization.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# API Error Taxonomy

## Purpose
Define consistent API error codes and responses.

## Inputs to request
- Current error responses and status usage.
- Client expectations for retries and messaging.
- Logging and observability requirements.

## Workflow
1. List common error categories and HTTP mappings.
2. Define error payload shape and fields.
3. Set guidelines for logging and client messaging.

## Output
- Error taxonomy table and examples.

## Quality bar
- Ensure errors are machine-parseable.
- Align retryable vs non-retryable semantics.

Related Skills

error-diagnostics-smart-debug

16
from diegosouzapw/awesome-omni-skill

Use when working with error diagnostics smart debug

error-detective

16
from diegosouzapw/awesome-omni-skill

Search logs and codebases for error patterns, stack traces, and anomalies. Correlates errors across systems and identifies root causes. Use PROACTIVELY when debugging issues, analyzing logs, or investigating production errors.

error-debugging-multi-agent-review

16
from diegosouzapw/awesome-omni-skill

Use when working with error debugging multi agent review

agent-error-detective

16
from diegosouzapw/awesome-omni-skill

Expert error detective specializing in complex error pattern analysis, correlation, and root cause discovery. Masters distributed system debugging, error tracking, and anomaly detection with focus on finding hidden connections and preventing error cascades.

Qiskit Cirq Quantum Error

16
from diegosouzapw/awesome-omni-skill

This skill covers the development of software for quantum computers, focusing on quantum algorithms, quantum error correction, and hybrid quantum-classical applications. It includes using quantum SDKs

Error Shape Taxonomy

16
from diegosouzapw/awesome-omni-skill

Organization-wide standard error response format covering error codes, categories, and structure that enables clients and monitoring tools to understand errors immediately.

Error Boundaries React

16
from diegosouzapw/awesome-omni-skill

Error boundaries are React components that catch JavaScript errors anywhere in their component tree, log those errors, and display a fallback UI instead of a component tree that crashed. Introduced in

api-error-handling

16
from diegosouzapw/awesome-omni-skill

Apply when designing error responses, implementing error handlers, and ensuring consistent error format across APIs.

aiwf:error-tracking

16
from diegosouzapw/awesome-omni-skill

Add Sentry v8 error tracking and performance monitoring to your project services. Use this skill when adding error handling, creating new controllers, instrumenting cron jobs, or tracking database performance. ALL ERRORS MUST BE CAPTURED TO SENTRY - no exceptions.

cfn-error-management

16
from diegosouzapw/awesome-omni-skill

Unified error handling, batching, and logging for CFN Loop. Use when you need to capture agent errors, batch multiple errors for processing, log structured error data, or categorize and recover from agent failures.

agent-error-coordinator

16
from diegosouzapw/awesome-omni-skill

Expert error coordinator specializing in distributed error handling, failure recovery, and system resilience. Masters error correlation, cascade prevention, and automated recovery strategies across multi-agent systems with focus on minimizing impact and learning from failures.

bgo

10
from diegosouzapw/awesome-omni-skill

Automates the complete Blender build-go workflow, from building and packaging your extension/add-on to removing old versions, installing, enabling, and launching Blender for quick testing and iteration.

Coding & Development