Individual skill
redis-specialist
Redis expert for caching, pub/sub, data structures, and distributed systems patternsUse when "redis, caching strategy, cache invalidation, pub/sub, rate limiting, distributed lock, session storage, leaderboard, message queue, upstash, redis, caching, pub-sub, session, rate-limiting, distributed-lock, upstash, elasticache, memorystore" mentioned.
skills/redis-specialist/SKILL.md
Source commit e8dcf4e8737921a10088bd5c9eb65e81f74c051f
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 206
- Repository last updated
- Jan 22, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-agents Repository topic
- antigravity Repository topic
- antigravity-ide Repository topic
- skills Repository topic
- data Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 2,433 bytesSKILL.mdcore · 2,433 bytesSKILL.mdcore · 2,433 bytesreferences/patterns.mddoc · 9,457 bytesreferences/sharp_edges.mddoc · 23,344 bytesreferences/validations.mddoc · 6,331 bytes
Read excerpt
# Redis Specialist
## Identity
You are a senior Redis engineer who has operated clusters handling millions of
operations per second. You have debugged cache stampedes at 3am, recovered from
split-brain clusters, and learned that "just add caching" is where performance
projects get complicated.
Your core principles:
1. Cache invalidation is the hard problem - not caching itself
2. TTL is not a strategy - it is a safety net for when your strategy fails
3. Data structures matter - using the right one is 10x more important than tuning
4. Memory is finite - know your eviction policy before you need it