reliability-resilience

Analyze failed behaviors to identify reliability risks and resilience strategies.

Updated Aug 23, 2026

Search Tags:#resilience #reliability #timeouts #incidents #retries #circuit-breaker #fault-isolation

Ready to run

npx skills add https://github.com/claushaas/claus-haas-ai-stuff --skill reliability-resilience

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: reliability-resilience
Source: https://github.com/claushaas/claus-haas-ai-stuff/tree/main/skills/reliability-resilience
Command: npx skills add https://github.com/claushaas/claus-haas-ai-stuff --skill reliability-resilience

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams analyze and improve reliability and resilience in systems without assuming architecture, tooling, or maturity. It guides identifying where and why failures occur, understanding blast radii, and designing context-appropriate safeguards that balance user experience, cost, and engineering effort.

Core Features & Use Cases

Failure mode analysis: map failure modes across critical paths, dependencies, and loads.
Guardrail design: propose timeouts, retries, circuit breakers, degradation strategies, and fault isolation appropriate to constraints.
Decision framework: translate observations into explicit, testable resilience strategies with cost and UX impact.
Use Cases: applies to services with flaky dependencies, timeouts, cascading failures, or unclear SLOs, guiding teams to implement concrete safeguards.

Quick Start

Review current failure signals, map critical paths, and generate three resilience options with trade-offs.

Frequently Asked Questions about reliability-resilience

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

FAQPage Schema

How do I prevent cascading failures when a downstream service dependency times out?▼

Prevent cascading failures by analyzing degraded behaviors to identify risks, then specifying testable resilience strategies like timeouts, retries, circuit breakers, and fault isolation to balance user experience and operational cost.

What is the best way to design resilience strategies for flaky service dependencies?▼

Design resilience strategies by mapping failure modes across critical paths and dependencies. A decision framework translates observations into explicit safeguards, generating options with clear trade-offs for cost, UX impact, and engineering effort.

How do circuit breakers and retries help with fault isolation during incidents?▼

Circuit breakers and retries provide fault isolation during incidents by stopping calls to failing dependencies. Analyzing system blast radii helps specify these testable degradation strategies to contain failures and maintain overall service reliability.

When should I implement degradation strategies for unclear SLOs and flaky dependencies?▼

Implement degradation strategies when analyzing failed behaviors reveals reliability risks from flaky dependencies. These strategies balance user experience and operational cost, providing context-appropriate safeguards even when service level objectives are unclear.

Can I analyze reliability risks without assuming specific architecture or tooling maturity?▼

Yes, you can analyze reliability risks without assuming architecture or tooling maturity. The approach guides identifying where and why failures occur, understanding blast radii, and designing context-appropriate safeguards for your specific constraints.

Why does retrying failed requests sometimes worsen system reliability during outages?▼

Retrying failed requests can worsen reliability during outages by increasing load on struggling services. Analyzing failure modes helps specify appropriate guardrails, balancing retry strategies with circuit breakers and fault isolation to prevent overload.