upstash / redis-js

The skill, also named redis-js, walks an agent through @upstash/redis: connecting over Upstash's HTTP-based REST API instead of a raw TCP connection, then using it for caching, session storage, rate limiting, leaderboards, and the full range of Redis data structures (strings, sorted sets, lists, hashes, sets), plus the newer full-text search extension via @upstash/search-redis and @upstash/search-ioredis. That REST design is the point of the whole library: it is built to run from serverless functions, Cloudflare Workers, and other places a persistent TCP connection either does not work or costs too much to hold open.

This is for someone already building on Upstash's own Redis service who wants an agent that writes correct calls against this specific client rather than a generic ioredis or node-redis pattern that will not work over HTTP. It needs a real account before anything runs: the skill's one dependency is an Upstash REST URL and token, which only exist once a database has been created in the Upstash console.

READ THE FULL ANALYSIS＋

There is exactly one skill here, not a library of them. upstash/redis-js is the SDK's own source repository; the skill documents that SDK, it does not curate a set of separate Redis workflows, so there is nothing else in this package to browse.

The README never mentions the skill at all. Everything upstash/redis-js's own README covers is the client itself: installation, basic usage, the release workflow, and telemetry, with no reference anywhere to an agent, a skill, or how to install one; we found it by reading the repository's skill file directly.