Memory Cache

What This Skill Does

The Memory Cache skill is a robust, Redis-backed storage layer designed for OpenClaw agents that require high-performance, temporary data persistence. Unlike standard file-based storage, this skill leverages the speed of Redis to handle state management, API response caching, and inter-agent communication. It ensures that agents remain stateless by design while providing a structured way to recall previous context or ephemeral data across different execution cycles. By adhering to the mandated 'mema:' namespace convention, the skill provides a clean, predictable way to organize data into categories like context, cache, and state, ensuring that memory cleanup and management are streamlined.

Installation

To integrate this skill into your environment, use the command: clawhub install openclaw/skills/skills/1999azzar/memory-cache. Ensure your environment has python3 installed and a running Redis instance reachable via your REDIS_URL environment variable. After installation, execute pip install -r requirements.txt within the skill directory to satisfy all dependency requirements.

Use Cases

• Agent State Persistence: Maintain conversation history or user preferences across disconnected sessions.
• API Rate Limiting & Optimization: Store frequently requested API results to reduce latency and stay within usage quotas.
• Sub-Agent Communication: Pass structured data between parallel or sequential agent tasks using synchronized shared memory.
• Session Management: Handle authentication tokens or temp session data that needs an automatic TTL (Time-To-Live) expiration.

Example Prompts

1. "Cache the response from the search API in mema:cache:last_search for the next 10 minutes."
2. "Check if there is an existing session context in mema:context:user_123 and retrieve it to continue our task."
3. "Run a scan to list all keys under the mema:state:* namespace so I can see which agent tasks are still active."

Tips & Limitations

• Always set a TTL (Time-To-Live) for your data to prevent memory leaks in your Redis database.
• Follow the namespace convention strictly; misuse of namespaces can lead to key collisions in multi-agent environments.
• This skill requires an external dependency (Redis); it is not a standalone storage solution and will fail if the Redis server is unavailable.