Redis HITL Gate

What problem does it solve?

This Skill prevents automated systems from silently falling back to less reliable methods (like filesystem searches) when the primary data source, Redis, is unavailable or returns unexpected results. It ensures user awareness and explicit authorization before any bypass occurs.

Core Features & Use Cases

• Human-in-the-Loop (HITL) Enforcement: Guarantees user interaction before deviating from the primary Redis data source.
• Controlled Fallback: Manages scenarios where Redis connection fails, the cache is empty, imports are broken, or queries yield no results.
• Evidence Logging: Documents all fallback events, user choices, and reasons for bypassing Redis.
• Use Case: When an agent needs to query ADG data from Redis but the connection fails, this Skill will prompt the user to choose between regenerating the cache, using a SQLite fallback, or stopping to investigate, preventing the agent from defaulting to a potentially inaccurate filesystem search without consent.

Quick Start

Ensure that before any operation attempts to query Redis, it first checks for Redis availability and presents the user with explicit fallback options if it is not available.