error-handlingDeep error handling workflow—taxonomy, user-visible vs internal errors, retries and idempotency, observability, and supportability. Use when standardizing fa...
Install via ClawdBot CLI:
clawdbot install mike47512/error-handlingGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Generated Apr 28, 2026
A payment gateway processing millions of transactions daily faces inconsistent HTTP status codes and retry storms during peak hours. Using this skill, the engineering team defines a taxonomy of error codes for insufficient funds, duplicate payments, and network timeouts, maps them to stable HTTP 4xx/5xx codes, and implements idempotency keys to prevent duplicate charges.
An online retailer experiences cart inconsistencies and duplicate orders due to naive retries during checkout. This workflow helps classify errors like stock conflicts and payment authorization failures, provides user-friendly messages with support reference IDs, and sets up exponential backoff retries for safe operations.
A SaaS platform with public REST APIs struggles with inconsistent error formats confusing developers. By applying this skill, the team creates a standard error taxonomy, maps to RFC 7807 Problem Details, and ships typed error classes in client SDKs, reducing integration support tickets by 40%.
A health tech company integrates with multiple EHR systems and faces ambiguous error responses causing data sync failures. This skill guides classification of validation, authentication, and dependency failures, ensures user-safe messaging without exposing PHI, and implements structured logging with trace IDs for audit trails.
Standardized error responses reduce support costs and improve developer experience for paying API consumers. Reliable error handling decreases churn and increases API adoption, directly protecting recurring revenue.
Clear error taxonomy and observability enable accurate SLA tracking and reporting on error rates. This model reduces liability risks and justifies premium pricing for guaranteed uptime.
Idempotent payment processing and user-friendly error messages reduce transaction failures and disputes. This increases trust and transaction volume, directly boosting commission revenue.
💬 Integration Tip
Start with Stage 1 (classify errors) and Stage 4 (retries & idempotency) as they provide immediate stabilization; then layer in observability (Stage 5) to measure impact.
Scored Apr 19, 2026
Automatically update Clawdbot and all installed skills once daily. Runs via cron, checks for updates, applies them, and messages the user with a summary of what changed.
Analyze Twitter content to uncover WordPress and Shopify client pain points, craft authority-building posts, and generate qualified inbound lead insights.
Real-time security monitoring for Clawdbot. Detects intrusions, unusual API calls, credential usage patterns, and alerts on breaches.
Interact with Uptime Kuma monitoring server. Use for checking monitor status, adding/removing monitors, pausing/resuming checks, viewing heartbeat history. Triggers on mentions of Uptime Kuma, server monitoring, uptime checks, or service health monitoring.
A clean, reliable system resource monitor for CPU load, RAM, Swap, and Disk usage. Optimized for OpenClaw.
Publish content to Mastodon. Use when you need to post a Mastodon status.