reliability

Enforce timeouts, retries, circuit breakers, and health checks in software designs.

6|3|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/alo-exp/silver-bullet --skill reliability-alo-exp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reliability
Source: https://github.com/alo-exp/silver-bullet/tree/main/forge/skills/reliability
Command: npx skills add https://github.com/alo-exp/silver-bullet --skill reliability-alo-exp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Every design, plan, and implementation MUST handle failure gracefully. Systems will fail — the question is how they respond to failure to maintain availability and user trust.

Core Features & Use Cases

  • Enforces explicit timeouts and robust failure handling on external calls.
  • Provides guidance for retries with exponential backoff, circuit breakers, and graceful degradation.
  • Defines health checks, observability requirements, and data integrity measures to survive partial outages.

Quick Start

Define timeouts, retry policies with backoff, and basic health checks for your critical dependencies.

Frequently Asked Questions about reliability

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

FAQPage Schema
How do I enforce graceful degradation and robust error handling across software designs?

Enforce graceful degradation by defining explicit timeouts, retries with exponential backoff, and circuit breakers for external calls. This ensures systems maintain availability and user trust when facing partial outages or dependency failures.

What are the best practices for implementing circuit breakers and exponential backoff?

Best practices for circuit breakers and exponential backoff involve defining explicit retry policies that progressively delay requests upon failure, preventing cascading system failures and allowing dependencies time to recover.

When do I need health checks and observability requirements for fault tolerance?

You need health checks and observability requirements for fault tolerance when designing systems that must survive partial outages. Defining health endpoints and data integrity measures ensures continuous availability during the planning and implementation phases.

How do I specify timeouts for external calls to prevent system failure?

Specify timeouts for external calls by enforcing explicit timeout rules during the design and implementation phases. This robust failure handling prevents indefinite hanging and maintains overall system availability when dependencies fail.

Does this approach to fault tolerance apply to infrastructure work and software reviews?

Yes, this fault tolerance approach applies directly to infrastructure work and software reviews. It guides teams to define timeouts, circuit breakers, and observability measures across all design, planning, and implementation phases to ensure robust error handling.