ericrisco/rsc-harness / skills/redis
redis
VerifiedUse when using Redis or any Redis-protocol store (Valkey, ElastiCache, Upstash, Dragonfly, Memorystore) as a cache, queue, rate limiter or distributed lock and it has to be CORRECT rather than merely connected — stampede-proof caching, locks that cannot release someone else's hold, race-free rate limits, and jobs that survive a worker crash. NOT durable SQL queues with SELECT FOR UPDATE SKIP LOCKED (that is `postgresdb`), NOT vector similarity search over embeddings (that is `vector-db`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 17.0 KB |
| evals/README.md | markdown | 812 B |
| evals/cases.yaml | config | 3.6 KB |
| references/caching.md | markdown | 5.4 KB |
| references/locks-and-rate-limiting.md | markdown | 5.7 KB |
| references/queues.md | markdown | 4.7 KB |
| scripts/verify.shexecutable | script | 7.4 KB |
evals/README.md
View on GitHub# redis — evals
`cases.yaml` holds the routing and capability checks for this skill. `should_trigger` are prompts
that must select `redis` (including the non-obvious lost-EXPIRE race and the `KEYS *` review trigger);
`should_not_trigger` are near-neighbours that must route to a named sibling (`postgresdb`, `vector-db`,
`fly-io`, `nextjs`, `clickhouse-analytics`) so the boundary is exercised, not just the centre. The
`capability` case is a three-bug scenario (stampede + lock + rate limiter) graded against the
`must_include` rubric. There is no automated runner here — feed each prompt to the skill-router under
test and confirm the selection, then judge the capability answer against its rubric by hand (or with an
LLM judge). Keep prompts phrased like a real developer would ask, not as keyword bait.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| deprecation-and-migrationaddyosmani/agent-skillsManages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when migrating a database schema in production, such as renaming or dropping a column without downtime (expand/contract). Use when deciding whether to maintain or sunset existing code. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| performance-optimizationaddyosmani/agent-skillsOptimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| agent-cost-reportthedotmack/claude-memBelievable agent cost report for any period, default the last 7 full days PT, not counting today. Measured tokens from Claude Code transcripts priced at OpenRouter list prices (ESTIMATED), measured provider spend when a sanctioned source exists, note-taker cost separate, Timing-style HTML/PDF plus report.json, line-items.csv, evidence.json. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| agent-cost-reportthedotmack/claude-memBelievable agent cost report for any period, default the last 7 full days PT, not counting today. Measured tokens from Claude Code transcripts priced at OpenRouter list prices (ESTIMATED), measured provider spend when a sanctioned source exists, note-taker cost separate, Timing-style HTML/PDF plus report.json, line-items.csv, evidence.json. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |