Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
redis avatar

Redis Core

redis/agent-skills

  • 1.6k installs
  • 94 repo stars
  • Updated July 9, 2026
  • redis/agent-skills

redis-core is a Redis skill for data structure selection and key naming conventions.

About

The redis-core skill provides foundational Redis modeling guidance for choosing among String, Hash, List, Set, Sorted Set, JSON, Stream, and Vector Set structures plus consistent colon-separated key naming. It helps agents design keys and structures that scale without hot-key anti-patterns or ambiguous namespaces. Patterns cover caching, leaderboards, queues, pub/sub, and vector search use cases with structure-specific tradeoffs. Agents apply redis-core before implementing Redis clients in application backends. Redis structure selection: String, Hash, List, Set, ZSet, JSON, Stream, Vector. Colon-separated consistent key naming conventions. Caching, queues, leaderboards, and vector search patterns. Scalable data model guidance without hot-key pitfalls. Foundational Redis modeling before client implementation. Choose Redis data structures and colon-separated key naming for scalable data models.

  • Redis structure selection: String, Hash, List, Set, ZSet, JSON, Stream, Vector.
  • Colon-separated consistent key naming conventions.
  • Caching, queues, leaderboards, and vector search patterns.
  • Scalable data model guidance without hot-key pitfalls.
  • Foundational Redis modeling before client implementation.

Redis Core by the numbers

  • 1,649 all-time installs (skills.sh)
  • +177 installs in the week ending Aug 4, 2026 (Skillselion tracking)
  • Ranked #299 of 4,347 Backend & APIs skills by installs in the Skillselion catalog
  • Data as of Aug 4, 2026 (Skillselion catalog sync)
From the docs

What redis-core says it does

choose the right data structure (String, Hash, List, Set, Sorted Set, JSON, Stream, Vector Set) and use consistent colon-separated key names
SKILL.md
npx skills add https://github.com/redis/agent-skills --skill redis-core

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs1.6k
repo stars★ 94
Last updatedJuly 9, 2026
Repositoryredis/agent-skills ↗

Which Redis data structure and key pattern fits this use case?

Choose Redis data structures and colon-separated key naming for scalable data models.

Who is it for?

Backend developers designing Redis caches, queues, or vector indexes.

Skip if: Skip when only Redis admin ops without application data modeling.

When should I use this skill?

User designs Redis keys, picks data structures, or models Redis schemas.

What you get

Redis schema with appropriate structures and colon-separated key names.

  • Key naming schema
  • Data structure selection guide
  • TTL and memory plan

By the numbers

  • Skill version 1.0.0 from redis/agent-skills

Files

SKILL.mdMarkdownGitHub ↗

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.

Use caseRecommended typeWhy
Simple values, countersStringAtomic INCR/DECR, SET/GET
Object with independently updated fieldsHashPer-field reads/writes, no whole-object rewrite
Queue, recent-N itemsListO(1) push/pop at ends
Unique items, membership checksSetO(1) SADD/SISMEMBER/SCARD
Rankings, score-based rangesSorted SetScore-ordered; ZADD/ZRANGE/ZRANK
Nested / hierarchical dataJSONPath-level updates, nested arrays, RQE indexing
Event log, fan-out messagingStreamPersistent, consumer groups
Vector similarityVector SetNative vector storage with HNSW

Common anti-pattern: stuffing a flat object into a serialized string. Updating one field means fetch + parse + mutate + rewrite. Use a Hash instead.

See references/choose-data-structure.md for full rationale and Python/Java examples.

2. Use consistent key names

Use colon-separated segments with a stable hierarchy:

{entity}:{id}:{attribute}
user:1001:profile
user:1001:settings
order:2024:items
session:abc123
article:987:likes
game:space-invaders:leaderboard

Rules of thumb:

  • Lowercase, colon-separated. No spaces, no mixed casing (User_1001_Profile is bad).
  • Keep keys short but readable — keys live in memory and appear in every command.
  • Don't use full URLs or long strings as keys. Extract a short identifier, or use a hash digest of the URL.
  • Prefix for multi-tenancy (tenant:42:user:7:cart) so scans and ACLs can target a tenant cleanly.
  • Be consistent. Pick one convention per service and apply it across all keys.

See references/key-naming.md for cleanup examples and edge cases.

References

Related skills

open.feishu.cnLark Openapi ExplorerInstantly explore, test, and generate calls against the full Lark (Feishu) OpenAPI surface without leaving their agent workflow.493klarksuiteLark EventConsume real-time events from Lark/Feishu as structured NDJSON streams inside AI agent workflows.387k16klarksuiteLark Openapi ExplorerWhen an existing Lark/Feishu skill or CLI command cannot fulfill a specific requirement and they need to discover and invoke the exact native OpenAPI endpoint.386k16kscrapegraphaiJust ScrapeQuickly search, crawl, extract structured JSON, or monitor web pages without writing custom scraping code.245k41larksuiteLark AppsQuery the current visibility and permission scope of a Lark (Feishu) app without writing HTTP client code.235k16kmattpocockDesign An InterfaceGenerate multiple radically different interface or API designs in parallel before committing to one.188k198k

FAQ

Which structures are covered?

String, Hash, List, Set, Sorted Set, JSON, Stream, and Vector Set.

What naming convention?

Consistent colon-separated key names across namespaces.

What use cases?

Caching, leaderboards, queues, streams, and vector search patterns.

Backend & APIsbackend
Browse by category
AI & AgentsFrontend & DesignBackend & DataDev ToolsAutomationTesting & ReviewSecurityMonitoring & CloudDocs & Planning
Design & frontend
Design systemsAnimation & motionAccessibility (a11y)CSS & TailwindUI designUXDesign to codeshadcn/uiLanding pagesBest design skills
Most searched skills
find-skillscavemanfrontend-designbrainstormingsystematic-debuggingstop-slopemil-design-engui-ux-pro-maxkarpathy-guidelinesweb-design-guidelinesreact-best-practicesgrill-meimprovemicrosoft-foundryagent-browser
Browse all listings
All agent skillsAll MCP serversAll marketplacesAll plugins

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.