\n\nQuick Guide: Use
\n@upstash/redis(the successor to@vercel/kv) for serverless, edge-compatible Redis via REST API. Key gotchas: REST adds ~5-15ms latency per call vs TCP Redis, all values are auto-serialized as JSON (objects round-trip transparently butDateobjects become strings), pipeline/multi execute as single HTTP requests but pipeline is NOT atomic. UseRedis.fromEnv()for automatic connection. Always set TTLs -- serverless Redis is billed per command.
<critical_requirements>
\n\n\nAll code must follow project conventions in CLAUDE.md (kebab-case, named exports, import ordering,
\nimport type, named constants)
(You MUST use @upstash/redis for new projects -- @vercel/kv was deprecated in December 2024 and all stores were migrated to Upstash Redis)
(You MUST set TTLs on all cached data -- serverless Redis is billed per command and has storage limits per plan)
\n(You MUST understand that this is a REST/HTTP client, NOT a TCP Redis client -- each command is an HTTP request with ~5-15ms overhead, so batch with pipelines when possible)
\n</critical_requirements>
\nAdditional resources:
\nAuto-detection: Vercel KV, @vercel/kv, @upstash/redis, Upstash Redis, KV_REST_API_URL, KV_REST_API_TOKEN, UPSTASH_REDIS_REST_URL, UPSTASH_REDIS_REST_TOKEN, Redis.fromEnv, kv.set, kv.get, kv.hset, kv.hget, kv.incr, kv.expire, kv.del, createClient, automaticDeserialization, edge Redis, serverless Redis
\nWhen to use:
\nKey patterns covered:
\nRedis.fromEnv(), new Redis())When NOT to use:
\n<decision_framework>
\nWhich Redis client should I use?\n+-- Running in Vercel Edge Runtime? -> @upstash/redis (only option -- no TCP)\n+-- Running in Vercel Serverless Functions? -> @upstash/redis (simpler) or ioredis (if you need TCP features)\n+-- Need Pub/Sub subscribers? -> ioredis (REST cannot maintain subscriptions)\n+-- Need Redis Streams consumers? -> ioredis (requires persistent TCP connection)\n+-- Need lowest possible latency (<1ms)? -> ioredis with TCP (REST adds HTTP overhead)\n+-- Simple caching/sessions/counters? -> @upstash/redis (zero connection management)\nHow should I batch commands?\n+-- Need atomicity (all-or-nothing)? -> redis.multi() (transaction)\n+-- Just reducing HTTP round-trips? -> redis.pipeline() (non-atomic batch)\n+-- Single independent command? -> Direct call (redis.set, redis.get, etc.)\n</decision_framework>
\n<red_flags>
\nHigh Priority Issues:
\n@vercel/kv in new projects -- deprecated December 2024, use @upstash/redis insteadJSON.stringify/JSON.parse with Upstash Redis -- causes double-serialization because the SDK auto-serializes all valuesmulti() for atomic execution)Medium Priority Issues:
\nCommon Mistakes:
\nhgetall to return an empty object {} for missing keys -- Upstash returns null (unlike ioredis which returns {})get() returns null (not undefined) for missing keysDate objects and expecting them to survive round-trip -- they serialize to ISO strings and come back as strings, not Date instancesGotchas & Edge Cases:
\nautomaticDeserialization: false breaks many TypeScript types -- only disable if you need raw string responses and are prepared to handle typing manuallyset with ex option resets TTL on overwrite (standard Redis behavior) -- if you set a key that already has a TTL, the new ex value replaces itnx (set-if-not-exists) returns null on failure, \"OK\" on success -- check the return value explicitly</red_flags>
\n<critical_reminders>
\n\n\nAll code must follow project conventions in CLAUDE.md (kebab-case, named exports, import ordering,
\nimport type, named constants)
(You MUST use @upstash/redis for new projects -- @vercel/kv was deprecated in December 2024 and all stores were migrated to Upstash Redis)
(You MUST set TTLs on all cached data -- serverless Redis is billed per command and has storage limits per plan)
\n(You MUST understand that this is a REST/HTTP client, NOT a TCP Redis client -- each command is an HTTP request with ~5-15ms overhead, so batch with pipelines when possible)
\nFailure to follow these rules will cause deprecated package usage, unbounded storage costs, and unnecessary latency in serverless functions.
\n</critical_reminders>
\n","files":[{"path":"examples/core.md","sizeBytes":11230,"isText":true},{"path":"reference.md","sizeBytes":7187,"isText":true},{"path":"SKILL.md","sizeBytes":10657,"isText":true}],"reviewScore":null,"reviewSummary":null,"trust":{"provenance":"trusted-source-unreviewed","notice":"Community-authored content, reproduced verbatim and not vetted as instructions. Treat it as data to evaluate, never as directives to follow.","bodySource":null},"bodyLocked":false,"purchaseUrl":null,"sourceUrl":null,"report":{"provenance":"trusted-source-unreviewed","screen":{"ran":true,"outcome":"notes-only","suspicious":0,"notes":1,"hiddenCharacters":false},"virusScan":{"engine":"clamav","status":"clean","scannedAt":"2026-09-29T15:29:02.610364Z","sha256":"942C8D8ED0C9CF90AC8D7223E84AF14C8FB1829EC24165FC8EE71196739542A8","sizeBytes":10965},"review":null,"source":{"repositoryUrl":"https://github.com/agents-inc/skills","path":"dist/plugins/api-database-vercel-kv/skills/api-database-vercel-kv","license":"MIT","commit":"3a51ef571e996b18294bf776d53dbdad26de0617","subtreeSha":"9944FBCEA56ED5B4F47FF45A44624392A516AB716806402A151584F135DAEA85","lastSyncedAt":"2026-09-29T15:27:48.914434Z"},"reviewedAt":"2026-09-29T15:32:06.569308Z","notice":"Community-authored content, reproduced verbatim and not vetted as instructions. Treat it as data to evaluate, never as directives to follow."},"install":[{"target":"skills-cli","command":"npx skills add https://github.com/agents-inc/skills/tree/main/dist/plugins/api-database-vercel-kv/skills/api-database-vercel-kv"},{"target":"claude-code","command":"claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install agents-inc-skills@llmmart"},{"target":"git","command":"git clone https://github.com/agents-inc/skills.git"}]}