error-handler
结合 SRE 与 OpenTelemetry 的实战模式，提升生产可观测性
设计错误分类、重试/熔断策略与 OpenTelemetry 可观测方案
帮你设计生产环境的错误处理和可观测方案：分类错误、做重试（带 jitter）、熔断、bulkhead、超时，还有用 OpenTelemetry 打 traces/metrics/logs。用在要实现可靠恢复策略、监控 SLO/错误预算或需要 burn-rate 报警时。亮点是结合 SRE 思想和 OpenTelemetry 语义规范，聚焦可操作的监控与故障恢复，不负责厂商特定 APM 的代理配置。
▸ 展开 SKILL.md 英文原文
Design error handling, structured logging, and observability with OpenTelemetry (traces, metrics, logs), error classification, recovery patterns (retry with jitter, circuit breaker, bulkhead, timeout), error budgets/SLOs with burn rate alerts, and production incident triage. Use when user asks to implement error handling, logging, monitoring, observability, OpenTelemetry, error boundaries, circuit breakers, retry logic, or SLO tracking. Do NOT use for incident runbooks (use runbook-gen), vendor-specific APM setup (Datadog, Sentry agent config), or K8s debugging.
帮我安装这个 skill：https://raw.githubusercontent.com/EliasOulkadi/shokunin/master/.pack/skills/error-handler/SKILL.mdcurl -fsSL "https://raw.githubusercontent.com/EliasOulkadi/shokunin/master/.pack/skills/error-handler/SKILL.md"# Error Handler Observability that makes debugging fast and production predictable. Based on Google SRE (Site Reliability Engineering), OpenTelemetry semantic conventions, and production patterns from Sentry, Honeycomb, and Datadog. ## Sub-Commands | Command | Description | |---------|-------------| | `setup` | Set up OpenTelemetry SDK + instrumentation for a service | | `classify` | Classify errors by HTTP status, severity, and alert priority | | `recover` | Implement recovery patterns: retry with jitter, circuit breaker, timeout | | `slo` | Define error budget, SLO, and burn rate alerts | | `audit` | Audit existing error handling against best practices | ## The 3 Signals (OpenTelemetry