Error Classification

Name: Error Classification
Availability: InStock
Author: Kolb

Classify software errors into retryability, source, severity, and domain categories.

Updated Aug 23, 2026

Search Tags:#logging #errors #escalation #retry #incident-management #exception-handling #error-classification

Ready to run

npx skills add https://github.com/mkolb22/zen-plugin --skill error-classification

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Error Classification
Source: https://github.com/mkolb22/zen-plugin/tree/main/skills/error-classification
Command: npx skills add https://github.com/mkolb22/zen-plugin --skill error-classification

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Errors in software systems often require manual triage and can cause delays. Error Classification automatically categorizes errors into actionable categories to determine the right response—retry, escalation, or fallback—reducing resolution time and noise.

Core Features & Use Cases

Taxonomy-driven error classification that assigns retryability, source, severity, and domain to every error.
Actionable decision guidance that maps classifications to concrete responses (retry with backoff, fail fast, escalate, fallback).
Framework-ready templates and integration hooks to plug into existing monitoring, logging, and incident workflows.

Quick Start

Provide an error instance to the classifier and observe an automated, evidence-based response plan.

Frequently Asked Questions about Error Classification

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I classify software errors to determine whether to retry or escalate?▼

You can classify software errors by assigning retryability, source, severity, and domain to each instance. This taxonomy-driven approach maps categorized failures to concrete response strategies like retry with backoff, fail fast, escalate, or fallback.

What is the best way to automate incident management triage for service failures?▼

Automating incident management triage involves categorizing errors into structured, actionable categories to determine the right response. This reduces manual triage effort and resolution time by providing evidence-based response plans for service failures and external dependencies.

How do I handle exception handling logic for external dependency failures?▼

Exception handling for external dependency failures is managed by classifying the error and applying a configurable strategy. The taxonomy determines if the system should automatically retry the operation, fail fast, escalate the incident, or use a fallback mechanism.

Can I integrate error classification into existing logging and monitoring workflows?▼

Yes, you can integrate error classification into existing logging and monitoring workflows. The system provides framework-ready templates and integration hooks designed to plug directly into your current incident management and logging infrastructure.

Does this error classification approach require any specific dependencies or components?▼

No dependencies or components are required to use this error classification approach. It operates independently to apply a taxonomy of retryability, source, severity, and domain to categorize failures across your software systems.

When should I use a fail fast strategy instead of a retry with backoff for user input errors?▼

You should use a fail fast strategy when the error taxonomy identifies a non-retryable source, such as invalid user inputs. Conversely, retry with backoff is applied when the classification determines the failure is transient and retryable across services.