Redis Connections

Shows you how to configure Redis clients without shooting yourself in the foot. The big wins are connection pooling (never create a connection per request), pipelining batches of independent commands, and using SCAN instead of KEYS in production. It also covers RESP3 client-side caching for hot keys and timeout tuning. Written by Redis, Inc., so the guidance is authoritative. Most valuable when you're setting up redis-py, Jedis, or Lettuce for the first time, or when you notice latency creeping into what should be fast Redis calls. The blocking commands section clears up a common confusion about BLPOP on multiplexed connections.

skills.sh installs: 3K
GitHub stars: 175
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add redis/agent-skills --skill redis-connections --agent claude-code

Installs into .claude/skills of the current project.

Files

Redis Connections

Client-side guidance for talking to Redis efficiently: how to share connections, how to batch commands, which commands not to call in production, when to turn on client-side caching, and how to set timeouts that fail fast without breaking healthy traffic.

When to apply

Creating or reviewing a Redis client setup (redis-py, Jedis, Lettuce, go-redis, NRedisStack).
Making many small Redis calls and wondering where the latency is going.
Iterating large keyspaces, sets, hashes, or lists.
Enabling client-side caching for hot keys.
Tuning connect / read / write timeouts.

1. Pool or multiplex — never one connection per request

The single biggest mistake in Redis client code is opening a new TCP connection for every operation. Always either:

Pool — keep N persistent connections that the application leases per call (redis-py ConnectionPool, Jedis JedisPooled, go-redis client).
Multiplex — share a single connection across all requests (Lettuce, NRedisStack).

SKILL.md on GitHub