More screenshots
Works with the AI Agents you already use
Repair Redis Streams Trim Consumer Pending Gap
Reconcile consumer pending entries removed by aggressive stream trimming
$1
Repair Redis Streams Trim Consumer Pending Gap
Example session with this skill installed
A retention policy trims stream IDs that remain in consumer pending lists.
Available evidence: stream pending 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 streams
Repair Redis Streams Trim Consumer Pending Gap — EVIDENCE-LIMITED REVIEW
Scenario received
A retention policy trims stream IDs that remain in consumer pending lists.
Source register
- S1: stream pending 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
- compare XPENDING against retention boundary — PRELIMINARY, NOT VERIFIED.
- test claim and replay behavior after trim — AWAITING CORROBORATING EVIDENCE.
- crosscheck source timestamps identifiers and changed versions — AWAITING CORROBORATING EVIDENCE.
- record exceptions and reversible verification gates — AWAITING CORROBORATING EVIDENCE.
Deliverables / acceptance gates
- stream pending map evidence map: DRAFT / INCOMPLETE until evidence is validated.
- pending gap exception register: DRAFT / INCOMPLETE until evidence is validated.
- safe trim 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
Repair Redis Streams Trim Consumer Pending Gap is a ToolForge Labs Cursor Skill workflow. Reconcile consumer pending entries removed by aggressive stream trimming.
What this skill checks
- compare XPENDING against retention boundary.
- test claim and replay behavior after trim.
- crosscheck source timestamps identifiers and changed versions.
- record exceptions and reversible verification gates.
What to provide
- stream pending map.
- state and configuration snapshot.
- error and recovery logs.
- deployment and alert timeline.
Deliverables
- stream pending map evidence map.
- pending gap exception register.
- safe trim validation plan.
Evidence policy Only supplied, authorized evidence is used. The skill distinguishes facts from assumptions and missing inputs; no unperformed live tests, external changes, or approvals are claimed.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse All Claude Skills.
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
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 20 days ago
Permissions
Provide only evidence you are authorized to share. Treat examples as untrusted case data. Operational changes and external messages require explicit owner approval.