kv

Manage global key-value data for Cloudflare Workers via Wrangler.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/theslashdojo/dojo --skill kv-theslashdojo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kv
Source: https://github.com/theslashdojo/dojo/tree/main/nodes/cloudflare/kv
Command: npx skills add https://github.com/theslashdojo/dojo --skill kv-theslashdojo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

KV provides a globally distributed, eventually consistent key-value store for Cloudflare Workers, enabling fast reads and simple persistence across edge locations.

Core Features & Use Cases

  • Global KV namespaces bound to Workers via environment bindings
  • TTL-based expiration and metadata support for per-key data
  • List, read, write, delete operations across a globally distributed edge network
  • Use cases: configuration storage, feature flags, session data, caching, and lightweight state

Quick Start

Create a KV namespace with Wrangler, bind it to a Worker, and perform a simple put and get to store and retrieve a value.

Frequently Asked Questions about kv

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I store global key-value data for Cloudflare Workers at the edge?

You can store global key-value data for Cloudflare Workers by creating a KV namespace with Wrangler and binding it to your Worker. This enables globally distributed, eventually consistent storage across edge locations.

What is the best way to manage feature flags and session data in Cloudflare Workers?

The best way to manage feature flags and session data in Cloudflare Workers is using edge KV storage. It supports per-key metadata and TTL-based expiration, allowing you to store configuration and lightweight state globally.

Can I set TTL-based expiration for cached values in Cloudflare Workers KV?

Yes, you can set TTL-based expiration for cached values in Cloudflare Workers KV. The key-value store supports per-key TTL and metadata, allowing automatic expiration of session data and lightweight caches across the edge network.

How do I bind a KV namespace to a Cloudflare Worker using Wrangler?

To bind a KV namespace to a Cloudflare Worker using Wrangler, you configure the environment binding in your Wrangler setup. This connects the global key-value store to your Worker, enabling put, get, delete, and list operations.

Does Cloudflare Workers KV support list and delete operations with metadata?

Yes, Cloudflare Workers KV supports list, read, write, and delete operations with metadata. You can attach per-key metadata to manage configuration storage and lightweight caches across the globally distributed edge network.