lingxling/awesome-skills-cn/upstash-redis
Claude Code and agent skill by lingxling/awesome-skills-cn
- community
Checking that the SKILL.md file is still in the repository.
Use the @upstash/redis HTTP client for caching, sessions, counters, and Redis data structures from serverless and edge runtimes without connection pooling.
Install
npx vskill@latest install lingxling/awesome-skills-cn/upstash-redisSKILL.md
The same SKILL.md was published earlier as lingxling/awesome-skills-cn/upstash-redis.
Upstash Redis
Overview
@upstash/redis is a Redis client that talks to an Upstash Redis database over HTTPS instead of a TCP connection. Because every command is a stateless HTTP request, it works in environments where a pooled TCP client is awkward or impossible: Vercel and Netlify functions, Cloudflare Workers, Deno, Bun, and Next.js middleware. The client serializes and deserializes JavaScript values automatically, so numbers and objects round-trip without manual JSON.parse.
When to Use This Skill
- Use when the user needs a cache, session store, counter, leaderboard, or
simple queue from a serverless or edge function.
- Use when the user mentions Upstash Redis,
UPSTASH_REDIS_REST_URL, or
@upstash/redis.
- Use when migrating an
ioredisornode-rediscall site to a runtime that
cannot hold a persistent TCP socket.
- Do not use for a self-hosted or non-Upstash Redis server; the client only
speaks the Upstash REST protocol. Use ioredis or node-redis there.
- Do not use for Redis administration or CLI work; see
redis-cli.
How It Works
Step 1: Configure credentials
Create a database in the Upstash console and copy the REST URL and token into environment variables. Never hardcode them.
Step 2: Create one client per module
On Cloudflare Workers, import from @upstash/redis/cloudflare and pass the worker env object: Redis.fromEnv(env).
Step 3: Call Redis commands as methods
Command names are lowercase methods (get, set, hset, zadd, incr). Values are auto-serialized; pass and receive native JavaScript types.
Examples
Example 1: Cache-aside with a TTL
Example 2: Batch commands in a pipeline
pipeline() batches independent commands into one round trip. It is not atomic; use redis.multi() for MULTI/EXEC or a reviewed server-side Lua script when commands must run as one unit.
Best Practices
- ✅ Read credentials with
Redis.fromEnv()or from a secrets manager. - ✅ Set a TTL (
{ ex: seconds }) on cache entries so stale data expires. - ✅ Namespace keys (
user:123,session:abc) to keep the keyspace readable. - ✅ Use
pipeline()ormget/msetinstead of many sequential awaits. - ❌ Don't
JSON.stringifyvalues beforeset; the client already does it. - ❌ Don't call
keys("*")in request handlers; usescanfor large keyspaces. - ❌ Don't store secrets or PII in Redis without a retention plan and TTL.
Limitations
- Requires an Upstash Redis database; it cannot connect to other Redis servers.
- Each command is an HTTP request, so latency is higher than a warm TCP
connection; batch with pipelines where it matters.
- Transactions (
multi()) do not roll back on runtime errors, andWATCHis
not available over REST; use a Lua script for atomic check-and-set.
- Pub/Sub subscribe and blocking commands (
BLPOP,XREAD BLOCK) are not
supported over the REST client.
- This skill covers the TypeScript client only. Python, Go, and other SDKs
differ in method names.
- This skill does not replace environment-specific validation, testing, or
expert review.
Security & Safety Notes
- The REST token grants full read/write access to the database. Keep it in
server-side environment variables; never ship it to a browser bundle.
- Use a read-only token from the console for read-only workloads.
- Commands such as
flushdbanddelare destructive; confirm with the user
before running them against a production database.
Common Pitfalls
- Problem:
getreturnsnullin production but works locally.
Solution: The deployment is missing UPSTASH_REDIS_REST_URL or UPSTASH_REDIS_REST_TOKEN; check the platform's environment settings.
- Problem: A number comes back as a string after
incron a value set
with JSON.stringify. Solution: Store the raw number (redis.set("n", 1)) and let the client serialize it.
Related Skills
@upstash-ratelimit- Rate limiting built on this client.@upstash-qstash- HTTP message queue and schedules when you need delivery
guarantees rather than a data store.
@redis-cli- Inspecting and administering Redis from the command line.@bullmq-specialist- Job queues on a TCP Redis you operate yourself.
Additional Resources
Security
- Security scanPassed, 90 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingantigravity-awesome-skills/skills/upstash-redis/SKILL.md
Popularity
- Repository stars
- 312
- Repository forks
- 53
- 7-day trend score
- 0
Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/lingxling/awesome-skills-cn/upstash-redis)