a5c-ai/babysitter / library/specializations/ai-agents-conversational/skills/redis-memory-backend
redis-memory-backend
VerifiedRedis backend for conversation state persistence and caching
SKILL.md
View on GitHub---
name: redis-memory-backend
description: Redis backend for conversation state persistence and caching
allowed-tools:
- Read
- Write
- Edit
- Bash
- Glob
- Grep
graph:
domains: [domain:software-engineering]
specializations: [specialization:ai-agents-conversational]
skillAreas: [skill-area:context-management, skill-area:caching-strategies]
roles: [role:ml-engineer, role:backend-engineer]
workflows: [workflow:feature-development, workflow:ml-model-lifecycle]
---
# Redis Memory Backend Skill
## Capabilities
- Configure Redis for conversation state storage
- Implement message history persistence
- Set up Redis caching for LLM responses
- Configure TTL-based memory expiration
- Implement Redis Pub/Sub for real-time updates
- Design efficient key schemas
## Target Processes
- conversational-memory-system
- chatbot-design-implementation
## Implementation Details
### Core Components
1. **Message Store**: RedisChatMessageHistory
2. **Cache**: LLM response caching
3. **State Store**: Conversation state persistence
4. **Pub/Sub**: Real-time updates
### Configuration Options
- Redis connection settings
- Key prefix configuration
- TTL settings
- Serialization format
- Cluster configuration
### Key Schema Patterns
- session:{session_id}:messages
- cache:llm:{prompt_hash}
- state:{user_id}:{key}
### Best Practices
- Use appropriate data structures
- Configure proper TTLs
- Implement connection pooling
- Monitor memory usage
### Dependencies
- redis
- langchain-community (RedisChatMessageHistory)
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |