Agent skill · software engineering · intellectronica
upstash-redis-kv
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.
Why this skill is useful
Provides specific commands and scripts for interacting with Upstash's Redis-compatible key-value store that the AI wouldn't reliably generate on its own.
What it needs
Requires bun installed locally. Requires upstash account access. About 6k tokens when loaded. Last updated 2026-04-25. 281 stars on the source repository.
What this skill does
Upstash Redis Key-Value Store Interact with Upstash's Redis-compatible key-value store using the REST interface. Script Location IMPORTANT: Always run with bun run, not directly. Configuration Environment Variables The script uses these environment variables by default: UPSTASHREDISRESTURL - The Upstash REST API URL UPSTASHREDISRESTTOKEN - The Upstash REST API token Overriding Credentials If the user provides credentials from another source (conversation context, a file, etc.), use the --url and --token flags to override environment variables: Priority: Command-line flags > Environment variables Command Reference String Commands Hash Commands Hashes store field-value pairs. Pass fields and values as alternating arguments: Examples: List Commands Lists are ordered collections. Values are pushed/popped from left (head) or right (tail): Examples: Set Commands Sets store unique, unordered members: Examples: Sorted Set Commands Sorted sets store members with scores for ranking: Examples: Key Commands Examples: Server Commands Command Options SET Options ZADD Options ZRANGE Options Output Format String values: Printed directly null/nil: Prints (nil) Objects/arrays: Pretty-printed as JSON Confirmation Behaviour Default: Ask for Confirmation Before executing any destructive operation (write, modify, or delete), you MUST ask the user for confirmation. This includes: Write operations: SET, SETNX, SETEX, PSETEX, MSET, MSETNX HSET, HSETNX LPUSH, RPUSH, LPUSHX, RPUSHX, LSET, LINSERT SADD ZADD Modify operations: INCR, INCRBY, INCRBYFLOAT, DECR, DECRBY APPEND, SETRANGE HINCRBY, HINCRBYFLOAT LREM, LTRIM, LMOVE ZINCRBY Delete operations: DEL, UNLINK HDEL LPOP, RPOP SREM, SPOP, SMOVE ZREM, ZREMRANGEBYRANK, ZREMRANGEBYSCORE, ZPOPMIN, ZPOPMAX FLUSHDB, FLUSHALL (extra caution) TTL/Rename operations: EXPIRE, EXPIREAT, PEXPIRE, PEXPIREAT, PERSIST RENAME, RENAMENX Example confirmation prompt: "I'm about to HSET user:1 with fields {name: "John", email: "john@example.com"}. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills intellectronica/skills--1c92cc