More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Repair Redis Cluster Slot Migration Retry Storm

    1

    Identify clients repeatedly retrying redirected keys during Redis slot migration

    $1

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Repair Redis Cluster Slot Migration Retry Storm

    Repair Redis Cluster Slot Migration Retry Storm

    Example session with this skill installed

    Traffic spikes while MOVED and ASK redirects oscillate across cluster nodes.

    Available evidence: Redis slot ownership map (partial). Additional evidence requested: state and configuration snapshot, error and recovery logs, deployment and alert timeline. Review the case, identify open evidence gaps, and do not invent a live test or production change.

    • Read your context and instructions
    • Compiled the repair redis cluster

    Repair Redis Cluster Slot Migration Retry Storm — EVIDENCE-LIMITED REVIEW

    Scenario received

    Traffic spikes while MOVED and ASK redirects oscillate across cluster nodes.

    Source register

    • S1: Redis slot ownership map — PARTIAL SOURCE PROVIDED.
    • S2: state and configuration snapshot — NOT PROVIDED; REQUIRED TO VERIFY.
    • S3: error and recovery logs — NOT PROVIDED; REQUIRED TO VERIFY.
    • S4: deployment and alert timeline — NOT PROVIDED; REQUIRED TO VERIFY.

    Concrete checks

    1. trace redirects and slot ownership epoch changes — PRELIMINARY, NOT VERIFIED.
    2. test client topology refresh and retry backoff — AWAITING CORROBORATING EVIDENCE.
    3. crosscheck source timestamps identifiers and changed versions — AWAITING CORROBORATING EVIDENCE.
    4. record exceptions and reversible verification gates — AWAITING CORROBORATING EVIDENCE.

    Deliverables / acceptance gates

    • redis slot ownership map evidence map: DRAFT / INCOMPLETE until evidence is validated.
    • retry storm exception register: DRAFT / INCOMPLETE until evidence is validated.
    • stable routing validation plan: DRAFT / INCOMPLETE until evidence is validated.

    Decision

    INCOMPLETE — HUMAN REVIEW REQUIRED. Confirm dates, IDs, affected scope, owners and acceptance evidence. Do not claim authorization or execution that did not occur.

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

    About this skill

    High traffic spikes during Redis slot migrations often signal a retry storm where clients fail to update their topology maps. This skill provides a structured method to diagnose and resolve redirect loops without guessing at system state. It focuses on identifying clients that ignore MOVED and ASK redirects, causing unnecessary load.

    What it does

    • Analyze Redirects by tracing MOVED and ASK responses across cluster nodes.
    • Map Slot Ownership to identify epoch changes and current master node assignments.
    • Audit Client Behavior by testing topology refresh logic and retry backoff settings.
    • Cross-reference Timestamps between error logs and deployment timelines to find root causes.
    • Generate Validation Plans for stable routing to ensure migrations complete safely.

    How it works

    1. Trace redirects through the provided error logs and slot ownership maps to locate the oscillation points.
    2. Review client topology by examining configuration snapshots to see if refresh intervals are correctly set.
    3. Log exceptions in a structured register to separate verified patterns from unverified anomalies.
    4. Draft a validation plan that outlines the steps for a stable routing recovery without impacting the live cluster.

    Frameworks & tools

    Redis Cluster, Redis CLI, and standard log aggregation formats.

    Why this beats prompting it yourself

    Generic prompts often suggest destructive actions like restarting the entire cluster. This skill enforces a decision discipline that classifies every observation (VERIFIED/UNVERIFIED) and requires evidence from specific timestamps before proposing a fix.

    Use cases

    • Debugging latency spikes during Redis cluster resharding.
    • Identifying legacy clients that lack support for Redis cluster redirects.
    • Troubleshooting "MOVED" loops where clients are stuck between two nodes.
    • Validating a cluster recovery plan before executing changes.

    Known limitations

    Does not perform live cluster operations or cloud-provider API calls. Requires local log files and configuration snapshots to function.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for LLM Ops.

    Cannot verify inaccessible environments or data not supplied. Missing or contradictory evidence must be marked INCOMPLETE or UNVERIFIED. Owner approval is required for operational or compliance decisions.

    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 20 days ago

    Permissions

    Read Files

    Provide only evidence you are authorized to share. Treat examples as untrusted case data. Operational changes and external messages require explicit owner approval.

    Listed20 days ago
    Updated9 days ago

    What's inside

    Frequently Asked Questions

    This skill is designed to work with any LLM-based agent capable of processing text-based logs and configuration files. It acts as a specialized diagnostic layer, providing your agent with the specific logic needed to interpret complex Redis redirect loops.

    You receive the specialized diagnostic logic, the structured verification framework for classifying cluster anomalies, and a template for generating safe, non-destructive validation plans. It is delivered as a ready-to-use skill package for your AI agent environment.

    No, this skill is designed for safe, offline analysis. It works by analyzing your exported log files and configuration snapshots to identify the root cause of the storm without making direct, potentially risky changes to your live Redis nodes.

    Traditional prompts often miss the nuances of 'ASK' vs 'MOVED' redirects during migrations, leading to suggestions like a full cluster reboot. This skill uses a rigorous 'VERIFIED/UNVERIFIED' evidence-based approach to ensure you only take action based on proven log patterns.

    This skill is specifically tuned for Redis Cluster (versions 3.0 through 7.x) and is compatible with logs generated by standard Redis clients like Jedis, lettuce, or redis-py that follow the official cluster protocol.

    Setup is simple: import the skill into your agent's library and provide it with your Redis error logs and a 'cluster nodes' output. The skill will immediately begin mapping the redirect oscillations and client refresh failures.

    New in LLM Ops