
Upstash Redis Kv
- 279 repo stars
- Updated April 25, 2026
- intellectronica/agent-skills
upstash-redis-kv is an agent skill that reads and writes Upstash Redis-compatible key-value data over the REST API.
About
upstash-redis-kv is an agent skill that lets developers and coding agents talk to Upstash’s serverless Redis-compatible store over HTTP. Install it when you need to save session context, rate-limit counters, feature flags, or short-lived lists during a build or prototype—especially in serverless or edge deployments where running Redis locally is awkward. The skill maps common Redis data types to REST operations so you do not paste ad hoc API snippets from docs each time. It fits agents building SaaS backends, CLI tools with cloud state, or multi-step workflows that must remember intermediate results. Scope is intentionally narrow: key-value and Redis primitives via Upstash, not self-hosted cluster administration or full ORM design.
- Read and write keys through Upstash Redis-compatible REST API
- Supports caches, counters, lists, sets, hashes, and sorted sets
- Invoked when the user asks for Upstash or Redis explicitly
- Designed for in-conversation persistence without a local Redis daemon
Upstash Redis Kv by the numbers
- Data as of Jul 20, 2026 (Skillselion catalog sync)
/plugin marketplace add intellectronica/agent-skills/plugin install upstash-redis-kv@intellectronica-skillsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| repo stars | ★ 279 |
|---|---|
| Last updated | April 25, 2026 |
| Repository | intellectronica/agent-skills ↗ |
What it does
Persist or read Redis-style KV data in the current agent session via Upstash REST without hand-rolling curl commands.
Who is it for?
SaaS and agent workflows on Vercel, Cloudflare, or other serverless hosts that already use or want Upstash for cache and ephemeral state.
Skip if: Production Redis cluster ops VMs, or teams that require a local Redis binary and are not using Upstash REST.
When should I use this skill?
When there is a need to save or retrieve key-value data, use Redis features (caching, counters, lists, sets, hashes, sorted sets, etc.) for the current interaction, or when the user explicitly asks to use Upstash or Redi
What you get
The agent performs consistent get/set and Redis-structure operations against your Upstash database for the current task.
- Executed KV reads and writes against Upstash
- Redis-structure operations (lists, sets, hashes, sorted sets) as requested
Files
Read and write to Upstash Redis-compatible key-value store via REST API. Use when there is a need to save or retrieve key-value data, use Redis features (caching, counters, lists, sets, hashes, sorted sets, etc.) for the current interaction, or when the user explicitly asks to use Upstash or Redis.
upstash-redis-kv
Source: ./plugins/upstash-redis-kv
{ "name": "upstash-redis-kv", "source": "./plugins/upstash-redis-kv", "version": "0.1.1770038631", "category": "productivity", "description": "Read and write to Upstash Redis-compatible key-value store via REST API. Use when there is a need to save or retrieve key-value data, use Redis features (caching, counters, lists, sets, hashes, sorted sets, etc.) for the current interaction, or when the user explicitly asks to use Upstash or Redis." }
Related skills
How it compares
Thin Upstash REST integration—not a full database migration or ORM skill.
FAQ
Who is upstash-redis-kv for?
Developers and agent users who want Upstash Redis KV from Claude Code, Cursor, or similar without writing raw REST each time.
When should I use upstash-redis-kv?
During Build when you must cache, count, or store lists, sets, hashes, or sorted sets for the current interaction, or when the user names Upstash or Redis.
Is upstash-redis-kv safe to install?
Check the Security Audits panel on this Prism page; REST credentials grant full KV access to your Upstash database and must stay out of commits and public logs.