redis_expert

Implements Redis caching strategies, Pub/Sub messaging, and data structure workflows.

Updated Jan 14, 2026
One-click install
npx skills add https://github.com/jvsandhu/agentic-skills --skill redis-expert-jvsandhu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: redis_expert
Source: https://github.com/jvsandhu/agentic-skills/tree/main/skills/redis_expert
Command: npx skills add https://github.com/jvsandhu/agentic-skills --skill redis-expert-jvsandhu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Designing Redis usage without a clear strategy leads to memory bloat, stale cache data, race conditions, and unbounded keys. This Skill provides a structured, phase-based workflow for modeling Redis data, choosing caching patterns, and applying advanced features correctly. ## Core Features & Use Cases - Data Modeling Guidance: Select the right Redis type (String, Hash, List, Set, Sorted Set), enforce key naming standards like app:module:id, and always assign TTLs. - Caching Strategy: Implement Cache-Aside patterns with proper invalidation logic so database updates stay in sync with Redis. - Advanced Patterns: Apply Pub/Sub for inter-service messaging, atomic operations with INCR or Lua scripts to prevent race conditions, and Streams for high-volume event sourcing. - Use Case: When building a session store or leaderboard, follow the checklist to pick Sorted Sets, set eviction policies like LRU, and verify connection pooling before deployment. ## Quick Start Ask the agent to design a Redis caching layer for your service, including key naming, TTLs, eviction policy, and invalidation logic.

Frequently Asked Questions about redis_expert

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose the right Redis data type for my use case?

Match the data type to your access pattern: Strings for simple values, Hashes for objects, Lists for queues, Sets for unique members, and Sorted Sets for ranked data like leaderboards. Always pair the choice with a key naming convention such as app:module:id.

How to implement cache-aside pattern with Redis?

The application checks Redis first; on a miss it reads from the database and writes the result into Redis with a TTL. When the database updates, delete or refresh the corresponding Redis key to prevent stale data.

Should every Redis key have a TTL?

Yes, defining an expiration for every key prevents unbounded memory growth and stale entries. Combine TTLs with an eviction policy such as LRU so Redis handles memory pressure predictably.

How do I prevent race conditions in Redis?

Use atomic operations like INCR for counters or Lua scripts for multi-step logic, since Redis executes them atomically. This avoids read-modify-write races when multiple clients update the same key concurrently.

When should I use Redis Streams instead of Pub/Sub?

Use Streams when you need persistent, replayable event logs for high-volume event sourcing. Pub/Sub is fire-and-forget messaging with no history, so it suits only transient notifications between services.