edgeone-makers-storage — Claude Code skill: setup and features
edgeone-makers-storage — a skill for Claude Code that configures storage on EdgeOne Makers. Sets up KV for Edge Functions and structures dynamic project data using Blob storage in Cloud Functions.
MIT 250 installs ★ 1,839 updated 2026-11-12
npx skills add TencentEdgeOne/edgeone-makers-tools --skill edgeone-makers-storage -a claude-codeWhat edgeone-makers-storage does
The skill manages persistent data architectures on EdgeOne Makers, where SQL, MongoDB, and ORMs are completely absent. Dynamic data like guestbook entries or user states must be structured directly inside Blob storage using key prefixes such as messages/<id>.json.
KV storage handles small key-value pairs up to 25 MB inside Edge Functions. The KV namespace binds as a global variable directly from the console, bypassing context.env. For Node.js Cloud Functions, files and records use the @edgeone/pages-blob package, which requires getStore({ name, consistency: "strong" }) to prevent stale reads.
Interacting with Blob during development requires linked project credentials obtained via edgeone login or -t <token>. Running edgeone makers dev with Blob or KV requires the -n <project-name> argument to avoid interactive prompts that hang automated environments.
What it helps with
- persist structured application records in Blob without SQL databases
- manage edge key-value pairs up to 25 MB using global KV bindings
- prevent stale reads by applying strong consistency across Blob stores
- run local development workflows non-interactively using CLI project flags
Example prompts for the agent
- Model user profile storage using EdgeOne Blob key prefixes
- Access our KV counter inside an Edge Function without context.env
- Initialize an EdgeOne Blob store with strong consistency
How to install edgeone-makers-storage
1Skills CLI (Vercel)
npx skills add TencentEdgeOne/edgeone-makers-tools --skill edgeone-makers-storage -a claude-code2Manually: put the files in place
~/.claude/skills/makers-storage/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/makers-storage/
1Skills CLI (Vercel)
npx skills add TencentEdgeOne/edgeone-makers-tools --skill edgeone-makers-storage -a codex2Manually: put the files in place
.agents/skills/makers-storage/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add TencentEdgeOne/edgeone-makers-tools --skill edgeone-makers-storage -a cursor2Manually: put the files in place
.cursor/skills/makers-storage/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install TencentEdgeOne/edgeone-makers-tools skills/edgeone-makers-tools/references/makers-storage2Manually: put the files in place
.github/skills/makers-storage/SKILL.md1Skills CLI (Vercel)
npx skills add TencentEdgeOne/edgeone-makers-tools --skill edgeone-makers-storage -a gemini-cli2Platform CLI
gemini skills install https://github.com/TencentEdgeOne/edgeone-makers-tools --path skills/edgeone-makers-tools/references/makers-storageManually: put the files in place
.devin/skills/makers-storage/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add TencentEdgeOne/edgeone-makers-tools --skill edgeone-makers-storage -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about edgeone-makers-storage
How to install edgeone-makers-storage in Claude Code?
Run npx skills add TencentEdgeOne/edgeone-makers-tools --skill edgeone-makers-storage -a claude-code.
What does edgeone-makers-storage do?
It provides architecture rules for EdgeOne Makers, routing file uploads and dynamic JSON data to Blob storage while keeping edge key-value pairs in KV.
What is required to run edgeone-makers-storage?
It requires the @edgeone/pages-blob npm package for Cloud Functions, an active account via edgeone login or -t <token>, and the -n <project-name> flag in local dev.
Source text
SKILL.md · MIT
---
name: edgeone-makers-storage
description: >-
KV and Blob storage services on EdgeOne Makers. KV for edge key-value pairs,
Blob for file/object storage in Cloud Functions. Covers SDK usage, setup, and troubleshooting.
pathPatterns:
- edge-functions/**
validate:
- pattern: "context\\.env\\.[A-Za-z_]*[Kk][Vv]"
message: "KV is a console-bound global variable, not on context.env — call my_kv.get(...) directly. See makers-storage/references/kv.md."
metadata:
author: edgeone
version: "1.0.0"
---
# EdgeOne Makers Storage
> 🗄️ **There is NO managed database on this platform** — no SQL, no MongoDB, no Prisma, no ORM. Do **not** reach for `sqlite`, `pg`, `mysql`, `mongodb`, or an in-memory array (it resets on every cold start / redeploy). **Blob IS your database.** Any dynamic data a generated site needs to persist — guestbook messages, uploaded drawings, votes, leaderboards, per-user save state, form submissions — is modeled as Blob keys. Model your "tables" as **key prefixes** (`messages/<id>.json`, `users/<uid>.json`). See [references/blob.md](references/blob.md) → "Blob as your backend".
> ⚠️ **Local dev does NOT always require login.** `edgeone makers dev` runs without authentication for **pure-static** previews. Login only becomes necessary through this chain: **using Blob ⇒ the project must be `link`ed ⇒ linking requires a logged-in account first.** So if (and only if) dev/deploy must read/write **Blob** (or any credentialed backend), run `edgeone login` (browser) or pass `-t <token>` before linking/starting dev. **If your site has no backend, skip login and just run `edgeone makers dev`.** See also makers-env-adaption (Login authentication + Project linking).
>
> ⛔ **When the project uses Blob/KV, ALWAYS pass `-n <project-name>` to `edgeone makers dev`.** Bare `edgeone makers dev` drops into an interactive "Link existing / Create and link" picker that hangs in sandbox / non-interactive environments. With `-n`, the CLI auto-creates the project if the name doesn't exist yet — one command, no separate step needed.
>
> 🔒 **Every Blob store: `getStore({ name, consistency: "strong" })` — never the string form `getStore("name")`.** The string form defaults to eventual consistency and causes "I just wrote but the next read returns stale/null" bugs. Full rule and rationale: [references/blob.md](references/blob.md) → IRON RULE (top of file).
EdgeOne Makers provides two storage services. **Choose based on your runtime and data type:**
| Storage | Runtime | Data Type | SDK | Use Case |
|---------|---------|-----------|-----|----------|
| **KV** | Edge Functions only | Small key-value pairs (≤ 25 MB) | Global variable (no npm) | Counters, config, session tokens, simple CRUD |
| **Blob** | Cloud Functions (Makers Functions) | Files & objects (images, docs, uploads) | `@edgeone/pages-blob` (npm) | User uploads, AI-generated content, file management |
## Decision Tree
```
Need to persist anything (records, lists, counters, uploads, save state)?
├─ Edge Function (V8 runtime, no npm)?
│ → KV Storage (global variable) → read references/kv.md
└─ Cloud Function (Node.js, has npm)? ← default for any real backend
├─ Files / images / large objects?
│ → Blob Storage → read references/blob.md
└─ Structured data (records, lists, counters, per-user state)?
→ Blob with setJSON / key prefixes → read references/blob.md
```
## Routing
| Task | Read |
|------|------|
| KV Storage (Edge Functions, global variable, put/get/delete/list) | [references/kv.md](references/kv.md) |
| Blob Storage (Cloud Functions, npm SDK, file upload/download, pre-signed URLs) | [references/blob.md](references/blob.md) |
© edgeone · MIT · TencentEdgeOne/edgeone-makers-tools