Back to Skills

redis-core

Core Redis modeling guidance — choose the right data structure (String, Hash, List, Set, Sorted Set, JSON, Stream, Vector Set) and use consistent colon-separated key names. Use when designing a Redis data model, caching objects, deciding between Hash and JSON, building counters, leaderboards, membership sets, or session stores, or when reviewing/cleaning up Redis key naming.

94stars22forksUpdated 8/4/2026

Security Assessment

Safe(98/100)
Security Score98/100

About redis-core

Redis Core is a data-modeling guidance skill from Redis, Inc. that helps developers make the two decisions which most affect Redis memory, performance, and maintainability: which data structure to use, and how to name keys. It solves the recurring problem of applications defaulting to a serialized string blob for everything, then paying fetch-parse-mutate-rewrite costs on every field update.

The skill centers on a decision matrix that maps access patterns to Redis types: Strings for simple values and atomic counters, Hashes for objects with independently updated fields, Lists for queues and recent-N items, Sets for uniqueness and membership, Sorted Sets for rankings and leaderboards, JSON for nested/hierarchical data with path-level updates, Streams for event logs and fan-out messaging, and Vector Sets for vector similarity with HNSW. It calls out the flat-object-in-a-string anti-pattern and recommends Hashes instead. The second half establishes key-naming conventions: lowercase colon-separated segments in a stable hierarchy (for example user:1001:profile), short but readable keys, tenant prefixes for multi-tenancy, and avoiding full URLs as keys. Reference files provide fuller rationale plus Python (redis-py) and Java (Jedis) examples, and the package ships eval suites and benchmark baselines used to measure the skill's effect across models.

The intended users are backend and platform engineers designing a Redis data model, building caches, counters, leaderboards, membership sets, or session stores, or reviewing and refactoring existing key names. It is a read-only conceptual reference: it prescribes conventions and shows illustrative code but does not execute anything against a live Redis instance, making it a safe design companion.

FAQ

What decisions does this skill help with?

Two: choosing the right Redis data structure for an access pattern, and applying consistent colon-separated key-naming conventions. It frames these as the choices that most drive memory, performance, and maintainability.

Does it run commands against my Redis server?

No. It is guidance and reference material only, with illustrative Python (redis-py) and Java (Jedis) snippets. Nothing connects to or modifies a live database.

When should I reach for a Hash versus JSON?

Use a Hash for a flat object whose fields are updated independently; use JSON for nested or hierarchical data needing path-level updates, nested arrays, and query-engine indexing. The skill's matrix lays out both.

Are there examples for cleaning up bad key names?

Yes. references/key-naming.md shows correct versus incorrect patterns, warns against spaces, mixed casing, and full-URL keys, and suggests hash digests for large binary keys.

Is there any evidence it improves results?

The package includes eval suites and benchmark baselines comparing model behavior with and without the skill across Claude Haiku, Sonnet, and Opus variants, reporting pass-rate and token deltas.

All Files

11 files
.cursor-plugin/plugin.json0.4 KB
View
evals/core/model-matrix.json0.6 KB
View
references/key-naming.md1.5 KB
View
evals/core/evals.json4.5 KB
View
evals/core/baselines/aggregate-benchmark.md2.6 KB
View
evals/core/baselines/README.md0.6 KB
View
SKILL.md3.0 KB
View
evals/core/baselines/aggregate-benchmark.json15.5 KB
View
evals/core/baselines/baseline.json0.4 KB
View
evals/core/baselines/model-matrix.json0.6 KB
View
references/choose-data-structure.md2.3 KB
View

Install redis-core

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill