Choose Redis structures and key conventions from the operations the application must perform.
Editorial review checked 2026-10-29 against this instruction snapshot. Supporting scripts and runtime behavior remain outside this editorial review.
The source compares common Redis data types and consistent key naming. It connects modeling choices with counters, membership, ranked data, sessions and object storage. That is useful before implementing a cache layout that later makes expiration, updates or efficient retrieval difficult.
Developers designing a new Redis-backed feature or reviewing an inconsistent key model.
The right structure depends on access patterns, size and concurrency. Choosing JSON or Hash is not a universal performance rule, and a naming convention alone does not prevent collisions between tenants or environments.
Unknown; inspect source requirements and supporting scripts.
Inspect the pinned source snapshot and its supporting files first. The command selects this skill through the open-source skills CLI. Node.js and agent-specific setup may be required. Installation can download code. Catalog ingestion never executes skill instructions or install scripts.
npx skills add https://github.com/redis/agent-skills/tree/a84871d065f398fed55e1633f66b66f731eb4e2b/skills/redis-core --skill redis-coreReview pinned skill folder ↗ · CLI documentation ↗
After source review, use npx skills check and npx skills update to inspect and apply upstream updates. Re-check changed instructions before running them.
Static review only. This is not a security audit or a guarantee of safety.
SKILL.md text only; scripts, dependencies and runtime behavior not audited.
Allowed tools declaration: Unknown. Runtime permissions and network behavior: Unknown.
A temporary folder-copy check, not an agent installation or runtime safety verdict.
3 files copied and checksummed from this exact source snapshot. No package code or installation scripts were executed.
Inventory SHA-256: 47eaa2f78a0ca87ab2c23935bdf4fef293ec27e0437be644ac571db563fc9f0c
85/100 · Metadata coverage 100% · Model 1.0
Scores summarize observable discovery signals. Popularity and repository activity apply to the whole repository. Unknown runtime safety earns no certification.
List required reads, updates, atomic operations and expiration rules, then select the smallest suitable structure. Define stable prefixes and identifiers, document TTL ownership and preserve a migration strategy if existing keys already use another layout.
Exercise representative reads and concurrent updates, inspect memory use and test expiration and missing-key behavior. Verify that tenant and environment boundaries remain distinct and that a model change does not silently abandon or reinterpret existing stored data.
Related by category; compare scope and dependencies before choosing an alternative.
Explore 360 feedback system as a data & databases workflow from sickn33/agentic-awesome-skills. Compare its source, maintenance and review signals before choosing it for your agent.
Repository star change: +147 over 41.38 hours. 2026-10-31
Explore access matrix as a data & databases workflow from sickn33/agentic-awesome-skills. Compare its source, maintenance and review signals before choosing it for your agent.
Repository star change: +147 over 41.38 hours. 2026-10-31
Explore adhx as a data & databases workflow from sickn33/agentic-awesome-skills. Compare its source, maintenance and review signals before choosing it for your agent.
Repository star change: +147 over 41.38 hours. 2026-10-31
Integrate Redis Agent Memory with explicit session and long-term memory boundaries.
Repository star change: +0 over 40.37 hours. 2026-10-31
Design Redis Cluster keys around actual multi-key operations and consistency requirements.
Repository star change: +0 over 40.37 hours. 2026-10-31
Configure Redis clients for bounded connection use, batched work and explicit timeouts.
Repository star change: +0 over 40.37 hours. 2026-10-31