Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Repair Cache Stampede Failures

    1

    Stop cache stampedes by repairing fill ownership, request coalescing, lock safety, refresh failures, TTL synchronization, and cold-cache overload.

    $1

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Repair Cache Stampede Failures

    Repair Cache Stampede Failures

    Example session with this skill installed

    Our Node/TypeScript product catalog uses Redis in front of PostgreSQL. A top-selling product key has a 5-minute TTL. When it expires, 200–500 concurrent requests all miss Redis and call the same expensive SQL query. We already have a Redis lock, but its lease is 2 seconds while the query sometimes takes 4–6 seconds, so another request can acquire the lock before the first fill completes. Waiting requests poll every 50 ms, and on refresh failure every caller bypasses cache. Repair the repository so one hot-key expiry does not create a thundering herd. Use local Redis/test fixtures and deterministic concurrency tests. Do not flush production Redis, change live infrastructure, or invent a new freshness SLA.

    • Read your context and instructions
    • Compiled the repair cache stampede

    Cache stampede found. A hot-key expiry triggers parallel SQL fills because the lock lease is shorter than the fill, followers poll aggressively, and refresh failure bypasses the cache per caller. The repair adds per-key coalescing, safer distributed ownership, generation protection, bounded follower behavior, concurrency tests, and fill metrics. Production capacity and freshness policy remain unverified.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Cache stampedes happen when a cache miss becomes a concurrency problem: hundreds of callers expire the same key, race for a lock, retry independently, or all fall back to the origin after one refresh failure.

    Repair Cache Stampede Failures gives an AI coding agent a repository workflow for tracing cache-fill ownership across application caches, Redis, loaders, background refresh jobs, distributed locks, retries, stale paths, and negative caching. It repairs single-flight/coalescing behavior, lock ownership, stale-owner protection, failure containment, TTL jitter, deterministic burst tests, and fill observability.

    It does not flush production caches, change live CDN/provider settings, invent staleness or capacity limits, or claim production safety from local tests.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Agents & Orchestration.

    Repairs repository-level cache-fill concurrency only. It cannot measure production capacity, choose acceptable staleness, change live CDN/Redis settings, prove cross-region locking behavior, or guarantee production load reduction without controlled rollout evidence.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 3 months ago

    Permissions

    Terminal / Shell
    Read Files
    Write Files

    Run on a clean branch. Use local/disposable cache and origin fixtures only. Keep production Redis credentials, cache dumps, customer payloads, API tokens, and private keys out of the workspace.

    Listed3 months ago
    Updated9 days ago

    What's inside

    Frequently Asked Questions

    This skill provides a specialized workflow that enables your AI agent to identify and fix race conditions, redundant cache-fill requests, and lock-safety issues that lead to origin server exhaustion.

    The skill is designed for repository-level integration and is compatible with most major AI coding agents that support custom workflows, including Cursor, Windsurf, and GitHub Copilot Workspace.

    The skill specializes in backend architectures utilizing Redis, distributed locking mechanisms, application-level loaders, and single-flight patterns for request coalescing.

    No, the skill focuses exclusively on the codebase level to improve logic and resilience; it does not possess the permissions to modify live production infrastructure or flush active caches.

    You receive a set of optimized workflow instructions, deterministic burst-test patterns for validation, and observability templates that allow your agent to trace fill ownership accurately.

    The skill includes guidance for creating deterministic burst tests locally or in CI, allowing you to verify that cache-fill coalescing works correctly before deploying changes to production.

    New in Agents & Orchestration