
Redis Core
Teaches you Redis data modeling fundamentals: picking the right structure for your access pattern and naming keys consistently. Covers when to use Hash versus JSON for objects, why serialized strings are usually a mistake, and the colon-separated naming convention that keeps large keyspaces maintainable. Most useful when you're starting a new Redis-backed feature or cleaning up a messy keyspace where half the keys are camelCase URLs and the other half are random prefixes. The guidance is opinionated but practical, with a clear decision table and real anti-patterns called out. Written by Redis, Inc., so it reflects current best practices rather than outdated Stack Overflow answers.
- skills.sh installs
- 4.4K
- GitHub stars
- 175
- last updated
- Aug 21, 2026
Install
$ npx -y skills add redis/agent-skills --skill redis-core --agent claude-codeInstalls into .claude/skills of the current project.
Files
Redis Core
Foundational guidance for modeling data in Redis. Covers data-type selection and key-name conventions — the two decisions that most directly drive memory, performance, and maintainability.
When to apply
- Caching objects, sessions, or per-user state.
- Counters, leaderboards, recent-items lists, unique-membership sets.
- Reviewing or refactoring Redis key names.
- Deciding between a Redis Hash and a JSON document for an entity.
1. Choose the right data structure
Pick the type that matches the access pattern, not just the shape of the data.
Sponsors
Details
- Repository
- github.com/redis/agent-skills
- Categories
- Backend & APIs, Code Review & Quality, AI & Agent Building, Databases
- First seen
- Jul 14, 2026