Individual skill

redis-pro-dev

Redis guidance — data structures, caching patterns, pub/sub, streams, transactions, and production operations.

skills/redis-pro-dev/SKILL.md

Read pinned source

Source commit faf37c0859ebf627bfcb5225e8057d088691e0ae

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 8, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
54
Repository last updated
Oct 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

## Overview

Redis is an in-memory data-structure server that teams use as a cache, session store, rate limiter, queue, pub/sub bus, and sometimes a primary database. Its power comes from the data structures — strings, hashes, lists, sets, sorted sets, streams — each with atomic operations that let you build correct concurrent systems without a database round trip.

The failure mode is treating Redis as magic fast storage without understanding eviction, persistence, and single-threaded command execution. This skill covers using the right structure for the job, caching patterns that stay correct, and operating Redis (persistence, clustering, memory) in production.

## When to use

- Adding caching to an application (choosing structure and pattern).
- Implementing rate limiting, leaderboards, sessions, or locks.
- Choosing between Redis pub/sub, Streams, lists, or a dedicated queue.
- Designing Redis key schemas and TTL strategies.
- Operating Redis in production (persistence, replication, Cluster, Sentinel).
- Debugging memory growth, eviction, or latency spikes.