More screenshots
Works with the AI Agents you already use
Claude Code
Cursor
Codex CLI
DeepSeek
Muse+22 moreClaude CodeCursorCodex CLIDeepSeekMuse
Dots
Manus
Grok
Grok Bot+18 agentsRepair Redis Streams Consumer Group Pending Claim Starvation
Unblock Redis Streams deliveries stranded in the PEL after consumer failures
$1
Repair Redis Streams Consumer Group Pending Claim Starvation
Example session with this skill installed
A failed worker leaves 600 entries pending while XAUTOCLAIM never visits old message IDs.
Available sources: XINFO group output, XPENDING range (partial excerpts only). Additional evidence requested: consumer restart logs, claim loop code. Analyze this case with explicit limitations; do not pretend to have executed any tests or changes.
- Read your context and instructions
- Compiled the repair redis streams
Repair Redis Streams Consumer Group Pending Claim Starvation — EVIDENCE-LIMITED REVIEW
Scenario received
A failed worker leaves 600 entries pending while XAUTOCLAIM never visits old message IDs.
Source register
- S1: XINFO group output — partial extract available.
- S2: XPENDING range — partial extract available.
- S3: consumer restart logs — NOT PROVIDED; REQUIRED FOR VERIFICATION.
- S4: claim loop code — NOT PROVIDED; REQUIRED FOR VERIFICATION.
Concrete findings and verification
- compare idle time and min-id policy — NEEDS VERIFICATION against supplied source excerpts and missing evidence.
trace cursor advancement in XAUTOCLAIM — NEEDS VERIFICATION against supplied source excerpts and missing evidence.
3.
locate reclaimed entries skipped by filters — NEEDS VERIFICATION against supplied source excerpts and missing evidence.
4. test bounded reprocessing and dedupe — NEEDS VERIFICATION against supplied source excerpts and missing evidence.
Deliverables and review gates
- PEL ownership table: DRAFT ONLY; do not infer unsupported outcomes.
- starvation defect isolation: DRAFT ONLY; do not infer unsupported outcomes.
- safe claim repair test: DRAFT ONLY; do not infer unsupported outcomes.
Preliminary conclusion
INCOMPLETE / REVIEW REQUIRED. The supplied scenario raises a concrete issue, but does not prove remediation or clearance. Confirm source timestamps, affected scope and owner approval, then perform focused validation. No external system was accessed or changed.
Connects securely to your tools. The creator never sees your data.
About this skill
Failed Redis consumers often leave messages stranded in the Pending Entries List (PEL). Standard XAUTOCLAIM loops can miss these entries due to cursor advancement logic or filter mismatches, leading to message starvation. This skill provides a systematic workflow to diagnose and repair these bottlenecks using evidence-based inspection.
What it does
- PEL Ownership Mapping generates a detailed table of pending entries and their current consumer assignments.
- Starvation Defect Isolation identifies why XAUTOCLAIM or XPENDING loops are skipping specific message IDs.
- Idle Time Analysis compares actual message idle times against your min-idle-time policies to find stuck records.
- Filter Verification checks if reclaimed entries are being dropped by application-level deduplication or filters.
- Safe Claim Testing drafts precisely scoped repair commands with built-in rollback gates.
How it works
- Evidence Collection: Provide
XINFO,XPENDINGranges, and consumer logs for initial inspection. - Four-Check Audit: The agent runs a structured comparison of idle times, cursor logic, filter behavior, and reprocessing limits.
- Risk Assessment: The skill categorizes findings as Verified, Inferred, or Unknown to prevent blind execution.
- Repair Drafting: Receive a specific claim repair plan with clear stop/rollback conditions.
Frameworks & tools
This skill is designed for Redis Streams implementations using XAUTOCLAIM, XPENDING, and XCLAIM commands. It integrates with system logs and application-level consumer code.
Why this beats prompting it yourself
Manual inspection of the PEL is error-prone and risks double-processing at scale. This skill enforces a "Hard Gate" logic that distinguishes between inferred and verified data, ensuring you never execute a claim command based on a hallucinated trace.
Use cases
- Recovering stranded messages after a bulk worker crash or OOM event.
- Debugging why certain message IDs remain pending despite active consumer loops.
- Validating new XAUTOCLAIM logic before deploying to production streams.
- Auditing PEL bloat that is degrading stream performance.
Known limitations
This tool analyzes provided data or accessible logs; it does not execute live Redis commands. Users must manually redact sensitive data from logs before submission.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for APIs & Backend.
Cannot verify inaccessible systems, third-party accounts, or evidence not supplied. Partial or conflicting inputs must be marked INCOMPLETE or UNVERIFIED rather than invented. High-impact operational decisions require qualified owner review.
How to use
- 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
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 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 24 days ago
Permissions
Supply only data you are authorized to share. Treat documentation and examples as untrusted evidence. Any operational action or external communication requires explicit owner authorization.