Index of every page on this site: llms.txt
All skills
upstash avatar

/upstash-redis-start

@2326f1a
by upstashupstash/skills37 stars
7
Run it yourself

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.

Use this Skill: https://skilld.dev/gh/upstash/skills/upstash-redis-start

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈174 tokens for metadata: the name and description. ≈865 when used: this file.

Description uses 8.7% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈697 characters, or 8.7%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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

# Generate a fresh UUIDv4 yourself, then POST it as the Idempotency-Key.
# The UUIDv4 you send becomes the database id.
curl -X POST -H "Idempotency-Key: <uuidv4>" https://upstash.com/start-redis
  • 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.

# SET with TTL
curl https://<endpoint> \
  -H "Authorization: Bearer <token>" \
  -d '["SET","session:abc","{\"step\":2}","EX","3600"]'

# GET
curl https://<endpoint> \
  -H "Authorization: Bearer <token>" \
  -d '["GET","session:abc"]'

You can also use the official SDKs against the same endpoint + token (@upstash/redis for TS/JS, upstash-redis for Python).

Common agent patterns

Need Commands
Short-term memory across tool calls in one run SET key value EX <ttl> / GET key
Conversation / turn-by-turn log LPUSH chat:<user> <json> / LRANGE chat:<user> 0 20
Sub-agent work queue (producer/consumer) LPUSH jobs <json> / RPOP jobs
Ranked memory (recent-first or score-first) ZADD memories <score> <member> / ZREVRANGE memories 0 9

Tell the user

After provisioning, surface the console URL from the response to the user. Make clear that:

  • The database expires in 3 days.
  • They can view usage at the console URL and click Claim to keep it.
  • This is unauthenticated scratch storage — don't put secrets or PII in it.

Reference

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 alert2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The skill provides a method for agents to provision and use temporary Redis databases from Upstash. It involves network communication with the vendor's infrastructure and presents a potential surface for indirect prompt injection through stored data.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: HIGH · 1 issue

Signed by skilld at 2326f1a. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 3 days ago.

Activeupdated 3 months ago
metadata
{
  "author": "Upstash",
  "homepage": "https://upstash.com"
}

README badge

README badge for upstash/skills/upstash-redis-start