Upstash Redis SDK skill
redis-js
Reference skill for @upstash/redis: data structures, caching, rate limits, locks and full-text search
- 985 ★ on the repository
- Last commit
- MIT
Minimal access
Why this level
- The guide is made of Markdown files and runs nothing, but code generated from it reaches the database with a token from environment variables
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/redis-jsDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewMinimal accessThe tool runs nothing and makes no network calls.
- The guide is made of Markdown files and runs nothing, but code generated from it reaches the database with a token from environment variables
This is third-party code. Review the repository files before installing.
What it does
The skills/ folder in the Upstash repository is packaged as the redis-js skill: a main SKILL.md plus about thirty topic guides. The agent loads the relevant file when it writes code for @upstash/redis, the HTTP-based Redis client for serverless functions and edge runtimes. The guides are grouped by task. Data structures: strings, hashes, lists, sets, sorted sets, JSON, streams, arrays and vector indexes. Patterns: caching, sessions, distributed locks, leaderboards and rate limiting. Separate sections cover pipelines and transactions, Lua scripts, TTL, serialization, error handling, replicas and full-text search. Migration pages cover moving from ioredis and redis-node.
Who it is for. Developers on Cloudflare Workers, Vercel and AWS Lambda who write Upstash Redis calls with Claude Code, Cursor or Codex.
Good fit when
- The agent writes a TTL cache for a Next.js API route and needs to know how the client serializes objects
- A serverless function needs rate limiting through the @upstash/ratelimit package
- A leaderboard on a sorted set should be built in one pipeline instead of a dozen separate requests
- A project moves from ioredis or redis-node to the HTTP client and the agent needs a command mapping
- Full-text search over hashes or JSON documents is needed inside Redis itself
Not a fit when
- The app talks to a regular Redis over TCP with ioredis: the guides cover only the Upstash HTTP client
- You need to administer a Redis server, tune a cluster or persistence: the skill covers the client library
- The task is better served by a Redis MCP server where the agent reads and writes keys in a live database itself
Example request
Add a 60-second cache for the /api/products route through Upstash Redis and a limit of 10 requests per minute per IPLimitations
- The skill targets TypeScript and JavaScript; examples in other languages are not covered.
- The guides match the SDK version from the same repository branch: older @upstash/redis releases may lack some commands, such as vector indexes and arrays.
- The README has no skill installer: you copy the skills/ folder into the agent's skills directory by hand and install the SDK with npm.
- The code needs an Upstash database and two values, the REST URL and the token.
How to disable. Delete the redis-js folder from the agent's skills directory, for example .claude/skills. The npm uninstall @upstash/redis command removes the installed package.
FAQ
How do I connect the redis-js skill to Claude Code?
Copy the skills/ folder from the repository into .claude/skills/redis-js in your project. The agent picks up SKILL.md by its description when a task mentions Redis or Upstash. The README has no separate skill install command.
Do I need the skill if the SDK is already in the project?
The agent needs the skill, the code does not: the SDK works without it. The guides save the agent a documentation search and suggest patterns such as distributed locks and pipelines.
Which environment variables do the examples need?
UPSTASH_REDIS_REST_URL and UPSTASH_REDIS_REST_TOKEN. Redis.fromEnv() reads them itself. Create the database in the Upstash console, keep the token in .env and do not commit it.
How is it different from a Redis MCP server?
The skill teaches the agent to write code with @upstash/redis. An MCP server lets the agent run commands in a live database. The first affects source files only, the second gets access to data.
Where is the documentation the skill builds on?
The main source is the docs at upstash.com/docs/redis/sdks/ts/overview. The guides in skills/ are short, with ready examples, and the list of supported commands is on the Redis compatibility page.
Discussion
No questions or reviews yet.
Related
SkillsRedis's official 15 skills teach an agent data structures, search, clustering, security and agent memory, plus a docs MCP server.
Hundreds of per-provider skills teach an agent to receive webhooks, verify signatures and handle events, with code examples.
Supabase's official skills: help an agent work with the database, Auth, Edge Functions and Postgres best practices
Three backend skills for agents that guard access, data and schema migrations: 2 of 150 runs had critical mistakes instead of 25.
The glide-mq skill teaches an agent to build job queues on Valkey and Redis Streams: workers, retries, schedules and workflows.
WorkOS Skills: AuthKit, SSO and RBAC for agents
WorkOS Skills
Official WorkOS skills: a router and 40 references on AuthKit, SSO, Directory Sync, RBAC, Vault and moves from Auth0 and Clerk
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Upstash Redis SDK (this card) | yes | 985 | ||
| Redis MCP Server | yes | not required | 642 | an MCP server lets the agent run commands in a live database, while this skill only teaches writing SDK code |
| Context7 | yes | API key | 64,735 | Context7 pulls documentation for any library, while this skill covers one SDK in more depth with patterns |
README in short
The repository page is about the @upstash/redis package itself: a connectionless HTTP Redis client for serverless, Cloudflare Workers, Fastly and Next.js. It covers npm install and a Deno import, a basic usage example and links to the docs and examples. The release section concerns package development. The README does not mention the skill, which sits in its own skills/ folder.