← Back to Skills Marketplace
mike47512

Error Handling

by mike47512 · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ✓ Security Clean
257
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install error-handling
Description
Deep error handling workflow—taxonomy, user-visible vs internal errors, retries and idempotency, observability, and supportability. Use when standardizing fa...
README (SKILL.md)

Error Handling

Consistent errors reduce support load and on-call pain. Design a taxonomy, stable codes, safe user messaging, and operator visibility—without leaking secrets or stack traces to clients.

When to Offer This Workflow

Trigger conditions:

  • Inconsistent HTTP status codes and response bodies
  • Retry storms or duplicate side effects from naive retries
  • Logs that cannot be tied to user-visible failures

Initial offer:

Use six stages: (1) classify errors, (2) map to transport, (3) user messaging, (4) retries & idempotency, (5) observability, (6) client SDKs & DX). Confirm REST/GraphQL/gRPC and sync/async patterns.

Stage 1: Classify Errors

Goal: Distinguish validation, authentication, authorization, not found, conflict, rate limit, dependency failure, and internal bugs.

Exit condition: Table or enum of codes with owning team and meaning.

Stage 2: Map to Transport

Goal: Correct HTTP 4xx/5xx; GraphQL errors with extensions; gRPC status codes; optional RFC 7807 Problem Details for JSON APIs.

Stage 3: User Messaging

Goal: Actionable copy for end users; opaque support reference id; no internal hostnames, SQL fragments, or stack traces in client responses.

Stage 4: Retries & Idempotency

Goal: Retry only safe or idempotent operations; exponential backoff with jitter; align with idempotency keys on writes.

Stage 5: Observability

Goal: Structured logs with error.code, trace_id, user_id (where allowed); metrics by error class; alerts on error-rate SLO burn.

Stage 6: Client SDKs & DX

Goal: Typed errors in SDKs; documented recovery; map codes to user-facing strings in apps consistently.

Final Review Checklist

  • Taxonomy and ownership defined
  • Transport mapping correct and consistent
  • User-safe messages with correlation ids
  • Retry policy matches idempotency story
  • Logs and metrics wired for ops

Tips for Effective Guidance

  • Separate expected validation errors from unexpected 500s in dashboards.
  • Pair with idempotency for write paths and queues.

Handling Deviations

  • Mobile offline: queue with explicit user-visible sync state.
Usage Guidance
This skill is a safe, high-level checklist for standardizing error handling and does not install code or ask for credentials. Before using it in production, adapt the taxonomy and logging recommendations to your privacy and compliance rules (avoid logging PII where prohibited), ensure the suggested correlation ids integrate with your tracing system, and translate the guidance into concrete code/SDK changes under your team’s review process.
Capability Analysis
Type: OpenClaw Skill Name: error-handling Version: 1.0.0 The skill bundle contains architectural guidance and workflow instructions for implementing standardized error handling in software systems. It focuses on best practices such as error taxonomy, idempotency, and preventing the leakage of sensitive information (stack traces/secrets) in API responses, with no executable code or malicious instructions present in SKILL.md or _meta.json.
Capability Assessment
✓ Purpose & Capability
The name/description promise a design workflow for error handling and the skill is purely instruction-only with no binaries, env vars, or installs — a proportional and expected footprint for a guidance/template skill.
✓ Instruction Scope
SKILL.md contains step-by-step design guidance (taxonomy, transport mapping, messaging, retries, observability, SDKs). It does not instruct the agent to read system files, access credentials, or call external endpoints; guidance to include user IDs in logs is appropriately qualified with "where allowed."
✓ Install Mechanism
No install spec and no code files are present, so nothing is written to disk or executed during install — this is the lowest-risk pattern and appropriate for a documentation-style skill.
✓ Credentials
The skill requires no environment variables, credentials, or config paths. The guidance mentions logging user_id where permitted but does not request secrets or access to external services, which is proportionate for its purpose.
✓ Persistence & Privilege
always is false and the skill is user-invocable; it does not request persistent system privileges or attempt to modify other skills or system configuration.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install error-handling
  3. After installation, invoke the skill by name or use /error-handling
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial public release introducing a comprehensive error-handling workflow across APIs and async workers. - Defines a six-stage process: error classification, transport mapping, user messaging, retries & idempotency, observability, and client SDK support. - Guides on building a stable taxonomy of error codes with operator visibility and safe user messages. - Provides clear recommendations for retry patterns and aligning idempotency in distributed systems. - Emphasizes structured logging, metrics by error class, and actionable user feedback.
Metadata
Slug error-handling
Version 1.0.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Error Handling?

Deep error handling workflow—taxonomy, user-visible vs internal errors, retries and idempotency, observability, and supportability. Use when standardizing fa... It is an AI Agent Skill for Claude Code / OpenClaw, with 257 downloads so far.

How do I install Error Handling?

Run "/install error-handling" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Error Handling free?

Yes, Error Handling is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Error Handling support?

Error Handling is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Error Handling?

It is built and maintained by mike47512 (@mike47512); the current version is v1.0.0.

More Skills
self-improving agent
Captures learnings, errors, and corrections to enable continuous improvement. Use when: (1) A command or operation fails unexpectedly, (2) User corrects Clau...
⬇ 463283 · by pskoett
Skill Vetter
Security-first skill vetting for AI agents. Use before installing any skill from ClawdHub, GitHub, or other sources. Checks for red flags, permission scope, and suspicious patterns.
⬇ 259410 · by spclaudehome
Polymarket
Query Polymarket prediction markets. Check odds, find trending markets, search events, track price movements.
⬇ 232503 · by joelchance
Self-Improving + Proactive Agent
Self-reflection + Self-criticism + Self-learning + Self-organizing memory. Agent evaluates its own work, catches mistakes, and improves permanently. Use when...
⬇ 200423 · by ivangdavila
Github
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
⬇ 191115 · by steipete
ontology
Typed knowledge graph for structured agent memory and composable skills. Use when creating/querying entities (Person, Project, Task, Event, Document), linkin...
⬇ 190156 · by oswalpalash

💬 Comments