Skill UI

A structured runbook for handling Apollo.io API outages and production failures. It guides users through severity classification (P1-P4), quick diagnosis scripting, implementing circuit breakers, and graceful degradation strategies to maintain service availability during incidents.

This skill details the architecture and implementation of a robust API Gateway, serving as the single entry point for multiple backend microservices. It centrally manages critical cross-cutting concerns, including path-based and header-based routing, JWT/OAuth2 authentication, rate limiting, load balancing, and circuit breaker protection. This pattern is essential for building resilient, scalable, and maintainable microservices architectures, significantly simplifying client integration and request management.

Automates circuit breaker setup inside API integrations, triggering whenever you ask about patterns or best practices, then guiding through code, validation, webhooks, and SDK-related configurations.

A comprehensive guide to building resilient and fault-tolerant data enrichment pipelines. Learn to implement critical patterns like credit budget circuit breakers, Dead Letter Queues (DLQs) for failed records, and health monitoring to ensure stability and cost control when integrating with external services like Clay.

This guide provides technical patterns for building fault-tolerant integrations with Customer.io. Learn to implement critical resilience techniques, including Circuit Breakers to prevent cascading failures, Retry with Jitter for handling transient errors, and Fallback Queues (using Redis) to ensure data continuity during service outages. Essential for robust, production-grade applications.

A comprehensive checklist and guide for deploying Deepgram integrations into a production environment. It covers critical areas including robust authentication practices, system resilience design (e.g., backoff strategies, circuit breakers), performance optimization (singleton clients, audio preprocessing), security measures (PII redaction), and mandatory monitoring setup (Prometheus metrics and alert rules). Essential for any go-live phase.

This utility provides comprehensive patterns for reliably integrating with the Deepgram API. It implements concurrency-aware rate limiting (using p-limit), exponential backoff with jitter for retries, and a circuit breaker pattern. Use this when building high-volume, mission-critical applications that must handle API quotas, 429 rate limit errors, and temporary service disruptions gracefully.

This skill provides patterns for building highly resilient applications that interact with external APIs. It covers crucial concepts like Exponential Backoff with Jitter, request queuing for bulk operations, and the Circuit Breaker pattern. Use this when your application needs to handle rate limit errors (429), transient network failures, or temporary service outages, ensuring reliable throughput and graceful degradation.

Provides structured error handling patterns, logging, retry/circuit breaker strategies, and observability workflows across JavaScript, Python, and Go; ideal when designing resilience, retries, aggregated logging, or alerting.

This skill provides guidance on implementing robust error handling strategies to build highly resilient applications. It covers advanced patterns such as circuit breakers, retries, and handling asynchronous errors, ensuring that the application fails gracefully and provides excellent debugging experiences for both developers and end-users.

This runbook provides comprehensive, step-by-step procedures for managing critical incidents involving Evernote integrations. It covers diagnosing API outages, resolving persistent rate limits, handling authentication failures, and recovering from data synchronization issues. Use this guide during production troubleshooting or service outages to ensure rapid and systematic incident response, including circuit breaker activation and graceful degradation strategies.

This skill provides robust, production-grade patterns for building fault-tolerant search service integrations, specifically targeting Exa. It covers implementing query fallback chains, circuit breakers to prevent cascading failures, exponential backoff for retries, and graceful degradation levels. Use this when designing mission-critical search features that must remain available and functional even if underlying services fail, rate limit, or suffer performance degradation.