Merge pull request #6 from upstash/DX-2639

DX-2639: add upstash-redis-start skill for zero-config Redis provisioning

Author: CahidArda

skills/upstash-redis-js/SKILL.md

@@ -39,6 +39,8 @@ UPSTASH_REDIS_REST_URL=https://your-redis.upstash.io
 UPSTASH_REDIS_REST_TOKEN=your-token-here
 ```
 
+> **No credentials yet?** If you're an agent that needs scratch Redis and the user hasn't provided a database, you can mint a temporary one with a single POST to `https://upstash.com/start-redis` (3-day TTL, no signup).
+
 ## Skill Files Overview
 
 ### Data Structures (skills/data-structures/)

skills/upstash-redis-start/SKILL.md

@@ -0,0 +1,76 @@
+---
+name: upstash-redis-start
+description: Provision a zero-config, no-signup Upstash Redis database for an AI agent via a single POST to `https://upstash.com/start-redis`. Use when an agent needs scratch Redis for short-term memory, conversation history, sub-agent work queues, or ranked recall and the user has not provided credentials. The database lives 3 days unless the user claims it.
+---
+
+# 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.
+
+Do **not** use this for: production workloads, anything tied to a user account, or anything storing PII / secrets / production credentials. The database is temporary and unauthenticated until claimed.
+
+## Create or re-fetch a database
+
+```bash
+# 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.
+
+```bash
+# 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
+
+- Service entry point (also serves the `GET` doc): https://upstash.com/start-redis
+- Full REST API: https://upstash.com/docs/redis/features/restapi
+- TS/JS SDK: https://upstash.com/docs/redis/sdks/ts
+- Python SDK: https://upstash.com/docs/redis/sdks/py

skills/upstash/SKILL.md

@@ -27,6 +27,10 @@ Lightweight guidance for using the Upstash Redis RateLimit TypeScript/JavaScript
 
 Work with the Upstash Redis TypeScript/JavaScript SDK for serverless Redis operations. Use for caching, session storage, rate limiting, leaderboards, full-text search (querying, filtering, aggregating) with Upstash Redis Search (different from regular FT.SEARCH), and all Redis data structures. Supports automatic serialization/deserialization of JavaScript types. Upstash Redis Search also available via @upstash/search-redis and @upstash/search-ioredis adapters for TCP clients.
 
+## [upstash-redis-start](upstash-redis-start/overview.md)
+
+Provision a zero-config, no-signup Upstash Redis database for an AI agent via a single POST to `https://upstash.com/start-redis`. Use when an agent needs scratch Redis for short-term memory, conversation history, sub-agent work queues, or ranked recall and the user has not provided credentials. The database lives 3 days unless the user claims it.
+
 ## [upstash-search-js](upstash-search-js/overview.md)
 
 Skills covering Upstash Search quick starts, core concepts, and TypeScript/JavaScript SDK usage. Use when a user asks how to get started, how indexing works, or how to use the TS client.

skills/upstash/upstash-redis-js/overview.md

@@ -34,6 +34,8 @@ UPSTASH_REDIS_REST_URL=https://your-redis.upstash.io
 UPSTASH_REDIS_REST_TOKEN=your-token-here
 ```
 
+> **No credentials yet?** If you're an agent that needs scratch Redis and the user hasn't provided a database, you can mint a temporary one with a single POST to `https://upstash.com/start-redis` (3-day TTL, no signup).
+
 ## Skill Files Overview
 
 ### Data Structures (skills/data-structures/)

skills/upstash/upstash-redis-start/overview.md

@@ -0,0 +1,71 @@
+# 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.
+
+Do **not** use this for: production workloads, anything tied to a user account, or anything storing PII / secrets / production credentials. The database is temporary and unauthenticated until claimed.
+
+## Create or re-fetch a database
+
+```bash
+# 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.
+
+```bash
+# 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
+
+- Service entry point (also serves the `GET` doc): https://upstash.com/start-redis
+- Full REST API: https://upstash.com/docs/redis/features/restapi
+- TS/JS SDK: https://upstash.com/docs/redis/sdks/ts
+- Python SDK: https://upstash.com/docs/redis/sdks/py