Agent skill · software engineering · upstash
upstash-redis-start
Provision a zero-config, no-signup, temporary Upstash Redis database for an AI agent with a single POST to https://upstash.com/start-redis, with no account, API key, or SDK setup required. Use when an agent needs scratch Redis right now and the user has not provided credentials, for short-term memory across tool calls, conversation history, a sub-agent work queue, ranked recall, or a quick prototype or demo. Covers idempotent creation and re-fetching credentials, calling the database through the body-style REST API or the official SDKs, and telling the user how to claim it. The database lives 3 days unless the user claims it; not for production data, PII, or secrets.
Why this skill is useful
Adds commands and patterns for interacting with a temporary Upstash Redis database that the AI wouldn't reliably generate on its own.
What it needs
About 3k tokens when loaded. Last updated 2026-07-14. 17 stars on the source repository.
What this skill does
Upstash Redis for Agents (start-redis) A zero-config Redis database for AI agents — no signup, no UI, no SDK setup. One HTTP request returns a working endpoint + token. Databases live for 3 days unless the user claims them. Use this when: The agent needs Redis right now and the user has not given you credentials. You want short-term memory across tool calls, conversation history, a sub-agent work queue, or recent-first ranked recall. This is built for quick experiments, prototypes, and demos rather than production workloads or anything tied to a real user account — the database is temporary and unauthenticated until claimed, so keep PII, secrets, and production credentials out of it. Create or re-fetch a database Sending your own UUIDv4 makes the first call retry-safe — if the response is lost, retrying with the same UUID returns the same database instead of minting a duplicate. Re-POST with the same Idempotency-Key to re-fetch credentials for an existing database. The header is optional. Omit it to mint a new database with a server-generated id (returned in the response — re-fetch later by passing that id back as Idempotency-Key). Only UUIDv4 is accepted. The response is markdown containing: Database ID, Endpoint, Token Metrics URL (JSON: uptime, commands, keys, throughput, memory, bandwidth) Expires date Console URL to share with the user (where they view usage and click Claim to keep the database) An inline quickstart for the body-style REST API Parse these out of the markdown response and use them directly — there is no separate JSON envelope. Calling the database (body-style REST) The returned endpoint speaks the Upstash Redis REST API. Prefer the body-style form: POST a JSON array as the body so you don't have to URL-encode the command. You can also use the official SDKs against the same endpoint + token (@upstash/redis for TS/JS, upstash-redis for Python). …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills upstash/upstash-redis-start