Cloudflare Manager技能：一站式管理Workers、KV、R2、Pages和DNS

Cloudflare Manager by ckorhonen/claude-skills

1 GitHub Stars

GitHub

安装命令

npx skills add https://github.com/ckorhonen/claude-skills --skill 'Cloudflare Manager'

自动化云服务开发运维

🇨🇳中文介绍

Cloudflare Manager

全面的 Cloudflare 服务管理技能，支持部署和配置 Workers、KV 存储、R2 存储桶、Pages、DNS 记录和路由。自动验证 API 凭证、提取部署 URL 并提供可操作的错误信息。

初始设置

首次使用此技能前：

安装依赖项

cd ~/.claude/skills/cloudflare-manager
bun install

配置 API 密钥

在项目根目录创建 .env 文件：

     CLOUDFLARE_API_KEY=your_api_token_here
     CLOUDFLARE_ACCOUNT_ID=your_account_id  # 可选，自动检测

获取 API 令牌 ：

 * 访问 <https://dash.cloudflare.com/profile/api-tokens>
 * 点击"创建令牌"
 * 使用"编辑 Cloudflare Workers"模板（或创建自定义令牌）
 * 所需权限：
   * 账户 > Workers 脚本 > 编辑
   * 账户 > Workers KV 存储 > 编辑
   * 账户 > Workers R2 存储 > 编辑
   * 账户 > Cloudflare Pages > 编辑
   * 区域 > DNS > 编辑（如果使用自定义域名）

3. 验证凭证

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

部署 Worker 容器

部署新的 Worker 容器沙盒：

# 使用技能
bun scripts/workers.ts deploy worker-name ./worker-script.js

执行过程 ：

创建新的 Worker 容器
部署 JavaScript/TypeScript 代码
自动提取并返回 Cloudflare 生成的 URL（例如 https://worker-name.username.workers.dev）
返回 Worker ID 和配置

示例对话 ：

User: "设置并部署一个名为 'api-handler' 的新 Cloudflare Worker 容器沙盒并返回 URL"
Claude: [使用 bun scripts/workers.ts deploy api-handler ./worker.js 部署 Worker]
       返回 URL: https://api-handler.username.workers.dev

退出代码 ：

0：成功 - Worker 已部署并返回 URL
1：失败 - 检查错误信息以获取详情

性能：部署通常在 2-5 秒内完成

创建和使用 KV 存储

创建 KV 命名空间并存储数据：

# 创建命名空间
bun scripts/kv-storage.ts create-namespace user-sessions
# 返回：命名空间 ID（例如 abc123def456）
# 保存此 ID 以绑定到 Workers

# 写入键值对
bun scripts/kv-storage.ts write <namespace-id> "session:user123" '{"userId":"123","token":"abc"}'

# 读取值
bun scripts/kv-storage.ts read <namespace-id> "session:user123"
# 返回：{"userId":"123","token":"abc"}

# 列出所有键（用于调试）
bun scripts/kv-storage.ts list-keys <namespace-id>

# 删除键
bun scripts/kv-storage.ts delete <namespace-id> "session:user123"

重要提示 ：KV 存储使用最终一致性。写入可能需要最多 60 秒才能全局传播。对于立即读取，请使用写入数据的同一边缘位置。

创建 R2 存储桶并上传文件

创建 R2 存储桶并管理对象：

# 创建存储桶
bun scripts/r2-storage.ts create-bucket media-assets

# 上传文件
bun scripts/r2-storage.ts upload media-assets ./images/logo.png logo.png

# 列出对象
bun scripts/r2-storage.ts list-objects media-assets

# 下载对象
bun scripts/r2-storage.ts download media-assets logo.png ./downloaded-logo.png

部署到 Cloudflare Pages

将静态站点或应用程序部署到 Pages：

# 创建 Pages 项目（或获取现有项目信息）
bun scripts/pages.ts deploy my-app ./dist
# 返回：https://my-app.pages.dev

# 设置环境变量
bun scripts/pages.ts set-env my-app API_URL https://api.example.com

# 为特定环境设置环境变量
bun scripts/pages.ts set-env my-app DEBUG true --env preview

# 获取部署 URL
bun scripts/pages.ts get-url my-app

自动提取的 URL ：Pages 脚本会自动从部署响应中提取并返回 Cloudflare 生成的 URL（例如 https://my-app.pages.dev）。

注意：API 创建项目结构，但对于实际文件上传，您需要 Wrangler CLI：

npx wrangler pages deploy ./dist --project-name=my-app

工作原理 ：该技能创建/验证 Pages 项目并返回 URL。对于包含文件的初始部署，Wrangler 处理复杂的多部分上传过程。

配置 DNS 和路由

创建 DNS 记录并配置 Worker 路由：

# 创建 DNS A 记录
bun scripts/dns-routes.ts create-dns example.com A api 192.168.1.1

# 将路由模式指向 Worker
bun scripts/dns-routes.ts create-route example.com "*.example.com/api/*" api-handler

设置包含 Worker、KV 存储和 R2 存储桶的完整应用程序：

为缓存创建 KV 命名空间

bun scripts/kv-storage.ts create-namespace app-cache

为媒体创建 R2 存储桶

bun scripts/r2-storage.ts create-bucket app-media

部署带绑定的 Worker

bun scripts/workers.ts deploy app-worker ./worker.js --kv-binding app-cache --r2-binding app-media

配置路由

bun scripts/dns-routes.ts create-route example.com "example.com/*" app-worker

更新 Worker 配置

更新现有 Worker 的代码或绑定：

# 更新 Worker 代码
bun scripts/workers.ts update worker-name ./new-worker-script.js

# 获取 Worker 详情
bun scripts/workers.ts get worker-name

# 列出所有 Workers
bun scripts/workers.ts list

对 KV 存储执行批量操作：

# 从 JSON 文件批量写入
bun scripts/kv-storage.ts bulk-write namespace-name ./data.json

# 删除多个键
bun scripts/kv-storage.ts bulk-delete namespace-name key1 key2 key3

如果缺少 .env 文件或未设置 CLOUDFLARE_API_KEY：

Error: CLOUDFLARE_API_KEY not found in environment

Solution: Create .env file in project root:
  echo "CLOUDFLARE_API_KEY=your_token_here" > .env

如果 API 令牌缺少所需权限：

Error: Insufficient permissions for Workers deployment

Required: Workers Scripts: Edit
Current: Workers Scripts: Read

Solution: Update token permissions at:
  https://dash.cloudflare.com/profile/api-tokens

如果请求过多：

Error: Rate limit exceeded (429)

Solution: Retry automatically with exponential backoff (3 attempts)

如果 API 无法访问：

Error: Failed to connect to Cloudflare API

Solution: Check internet connection and retry

切勿提交 .env 文件 - 始终添加到 .gitignore
使用基于令牌的身份验证（而非 API 密钥）
定期轮换令牌（建议每 90 天）
使用最小权限原则：仅授予所需权限
通过 Wrangler CLI 存储密钥：wrangler secret put SECRET_NAME

部署 Workers 以最小化延迟（它们在 Cloudflare 边缘运行）
对频繁读取的数据使用 KV 存储（非频繁写入）
对大文件使用 R2（KV 每个键限制为 25MB）
启用具有适当 TTL 的缓存
保持 Worker 脚本小于 1MB 以实现更快的冷启动

开发工作流程 ：

首先在本地测试：wrangler dev 用于本地测试
在生产前使用暂存环境
令牌更新后验证凭证：bun scripts/validate-api-key.ts
监控 Worker 日志：wrangler tail worker-name
为 Worker 版本化：使用类似 api-v1、api-v2 的名称

命名约定 ：

Workers：使用描述性名称（例如 user-auth-worker 而非 worker1）
KV 命名空间：包含用途（例如 app-sessions、api-cache）
R2 存储桶：使用小写字母和连字符（例如 media-assets-prod）
在整个基础设施中保持一致

资源管理 ：

删除未使用的 Workers、命名空间和存储桶
在 Cloudflare 仪表板中监控使用情况
免费层限制：Workers 每天 100,000 个请求
设置账单提醒以避免意外

对于高级场景，包括：

复杂路由配置
多区域部署
自定义域名设置
Worker 到 Worker 通信
Durable Objects 集成
批量操作和迁移

请参阅 examples.md 获取全面的示例和模式。

所有脚本位于 ~/.claude/skills/cloudflare-manager/scripts/：

validate-api-key.ts ：验证 API 凭证并显示权限
workers.ts ：部署、更新和管理 Workers
kv-storage.ts ：创建和管理 KV 命名空间和键值对
r2-storage.ts ：创建和管理 R2 存储桶和对象
pages.ts ：部署和配置 Cloudflare Pages 项目
dns-routes.ts ：配置 DNS 记录和 Worker 路由
utils.ts ：用于 API 调用和错误处理的共享实用程序

启动模板位于 ~/.claude/skills/cloudflare-manager/templates/：

worker-template.js ：带有 fetch 处理程序的基本 Worker 模板
wrangler.toml.template ：Wrangler 配置模板

常见问题和解决方案

问题："Worker 部署失败，未知错误"

症状：部署命令以错误代码 1 退出，无特定错误信息

解决方案 ：

检查脚本语法：node --check ./worker.js
验证文件存在：ls -lh ./worker.js
重新验证 API 密钥：bun scripts/validate-api-key.ts --no-cache
检查 Worker 名称是否有效（仅限字母数字、连字符、下划线）

问题："KV 命名空间未找到"

症状：尝试读取/写入命名空间时出错

解决方案 ：

列出所有命名空间：bun scripts/kv-storage.ts list-namespaces
验证您在命令中使用的是命名空间 ID（而非名称）
检查命名空间是否未被删除
确保 API 令牌具有 KV 存储权限

问题："R2 存储桶已存在" 或 "存储桶名称已被占用"

症状：无法使用所选名称创建存储桶

解决方案 ：

存储桶名称必须在所有 Cloudflare 账户中全局唯一
尝试更具体的名称：使用 my-app-media-2024 而非 media
使用现有存储桶：bun scripts/r2-storage.ts list-buckets
名称必须为 3-63 个字符，仅限小写字母/数字/连字符

问题："Pages 部署超时" 或 "部署挂起"

症状：部署未完成，保持挂起状态

解决方案 ：

检查部署状态：bun scripts/pages.ts list-deployments project-name
在仪表板中查看：https://dash.cloudflare.com/pages
大型部署（>1000 个文件）可能需要 5-10 分钟
如果卡住则取消并重试：删除项目并重新创建

问题："DNS 记录创建失败"

症状：无法创建 DNS 记录或路由

解决方案 ：

验证区域存在：bun scripts/dns-routes.ts list-zones
确保域名已添加到 Cloudflare 并处于活动状态
检查名称服务器是否指向 Cloudflare：dig NS yourdomain.com
验证 API 令牌具有区域 > DNS > 编辑权限

问题："API 速率限制超出 (429)"

症状：命令因"请求过多"而失败

解决方案 ：

脚本会自动使用指数退避重试
手动重试前等待 1-2 分钟
减少并发操作
速率限制：每 5 分钟 1200 个请求

问题："环境中未找到 CLOUDFLARE_API_KEY"

症状：命令立即因环境错误而失败

解决方案 ：

在项目根目录（而非技能目录）创建 .env 文件
验证文件内容：cat .env | grep CLOUDFLARE_API_KEY
确保没有额外空格：CLOUDFLARE_API_KEY=token（= 周围无空格）
从存在 .env 的项目根目录运行命令

快速修复 ：

cd /path/to/your/project
echo "CLOUDFLARE_API_KEY=your_token_here" > .env
bun scripts/validate-api-key.ts

API 密钥从不记录或显示在输出中
所有 API 请求均使用 HTTPS
用户输入在 API 调用前经过验证
破坏性操作（删除）需要确认
权限缓存 24 小时以最小化令牌暴露

🇺🇸English

Cloudflare Manager

Comprehensive Cloudflare service management skill that enables deployment and configuration of Workers, KV Storage, R2 buckets, Pages, DNS records, and routing. Automatically validates API credentials, extracts deployment URLs, and provides actionable error messages.

Initial Setup

Before using this skill for the first time:

Install Dependencies

cd ~/.claude/skills/cloudflare-manager
bun install

Configure API Key

Create a .env file in your project root:

     CLOUDFLARE_API_KEY=your_api_token_here
     CLOUDFLARE_ACCOUNT_ID=your_account_id  # Optional, auto-detected

Getting your API token :

 * Visit <https://dash.cloudflare.com/profile/api-tokens>
 * Click "Create Token"
 * Use "Edit Cloudflare Workers" template (or create custom token)
 * Required permissions: 
   * Account > Workers Scripts > Edit
   * Account > Workers KV Storage > Edit
   * Account > Workers R2 Storage > Edit
   * Account > Cloudflare Pages > Edit
   * Zone > DNS > Edit (if using custom domains)

3. Validate Credentials

Run validation to verify your API key and check permissions:

     cd ~/.claude/skills/cloudflare-manager
     bun scripts/validate-api-key.ts

Expected output :

     ✅ API key is valid!
     ℹ️  Token Status: active
     ℹ️  Account: Your Account Name (abc123...)
     
     🔑 Granted Permissions:
       ✅ Workers Scripts: Edit
       ✅ Workers KV Storage: Edit
       ✅ Workers R2 Storage: Edit

Troubleshooting validation :

 * If validation fails with 401/403: Check your API token is correct in `.env`
 * If validation fails with network error: Check internet connection
 * Use `--no-cache` flag to force fresh validation: `bun scripts/validate-api-key.ts --no-cache`

Current API Permissions

Run bun scripts/validate-api-key.ts to populate this section with your current permissions.

Quick Start Guide

Deploy a Worker Container

To deploy a new worker container sandbox:

# Using the skill
bun scripts/workers.ts deploy worker-name ./worker-script.js

What happens :

Creates new worker container
Deploys JavaScript/TypeScript code
Automatically extracts and returns Cloudflare-generated URL (e.g., https://worker-name.username.workers.dev)
Returns worker ID and configuration

Example conversation :

User: "Set up and deploy a new cloudflare worker container sandbox named 'api-handler' and return the URL"
Claude: [Deploys worker using bun scripts/workers.ts deploy api-handler ./worker.js]
       Returns URL: https://api-handler.username.workers.dev

Exit codes :

0: Success - worker deployed and URL returned
1: Failure - check error message for details

Performance : Deployment typically completes in 2-5 seconds

Create and Use KV Storage

To create a KV namespace and store data:

# Create namespace
bun scripts/kv-storage.ts create-namespace user-sessions
# Returns: Namespace ID (e.g., abc123def456)
# Save this ID for binding to workers

# Write key-value pair
bun scripts/kv-storage.ts write <namespace-id> "session:user123" '{"userId":"123","token":"abc"}'

# Read value
bun scripts/kv-storage.ts read <namespace-id> "session:user123"
# Returns: {"userId":"123","token":"abc"}

# List all keys (useful for debugging)
bun scripts/kv-storage.ts list-keys <namespace-id>

# Delete a key
bun scripts/kv-storage.ts delete <namespace-id> "session:user123"

Important : KV storage uses eventual consistency. Writes may take up to 60 seconds to propagate globally. For immediate reads, use the same edge location where you wrote the data.

Create R2 Bucket and Upload Files

To create an R2 bucket and manage objects:

# Create bucket
bun scripts/r2-storage.ts create-bucket media-assets

# Upload file
bun scripts/r2-storage.ts upload media-assets ./images/logo.png logo.png

# List objects
bun scripts/r2-storage.ts list-objects media-assets

# Download object
bun scripts/r2-storage.ts download media-assets logo.png ./downloaded-logo.png

Deploy to Cloudflare Pages

To deploy a static site or application to Pages:

# Create Pages project (or get existing project info)
bun scripts/pages.ts deploy my-app ./dist
# Returns: https://my-app.pages.dev

# Set environment variable
bun scripts/pages.ts set-env my-app API_URL https://api.example.com

# Set environment variable for specific environment
bun scripts/pages.ts set-env my-app DEBUG true --env preview

# Get deployment URL
bun scripts/pages.ts get-url my-app

Auto-extracted URLs : The Pages script automatically extracts and returns the Cloudflare-generated URL (e.g., https://my-app.pages.dev) from the deployment response.

Note : The API creates the project structure, but for actual file uploads, you'll need Wrangler CLI:

npx wrangler pages deploy ./dist --project-name=my-app

Why this works : The skill creates/verifies the Pages project and returns the URL. For the initial deployment with files, Wrangler handles the complex multipart upload process.

Configure DNS and Routes

To create DNS records and configure worker routes:

# Create DNS A record
bun scripts/dns-routes.ts create-dns example.com A api 192.168.1.1

# Route pattern to worker
bun scripts/dns-routes.ts create-route example.com "*.example.com/api/*" api-handler

Common Workflows

Multi-Service Setup

To set up a complete application with worker, KV storage, and R2 bucket:

Create KV namespace for caching

bun scripts/kv-storage.ts create-namespace app-cache

Create R2 bucket for media

bun scripts/r2-storage.ts create-bucket app-media

Deploy worker with bindings

bun scripts/workers.ts deploy app-worker ./worker.js --kv-binding app-cache --r2-binding app-media

Configure route

bun scripts/dns-routes.ts create-route example.com "example.com/*" app-worker

Update Worker Configuration

To update an existing worker's code or bindings:

# Update worker code
bun scripts/workers.ts update worker-name ./new-worker-script.js

# Get worker details
bun scripts/workers.ts get worker-name

# List all workers
bun scripts/workers.ts list

Bulk KV Operations

To perform bulk operations on KV storage:

# Bulk write from JSON file
bun scripts/kv-storage.ts bulk-write namespace-name ./data.json

# Delete multiple keys
bun scripts/kv-storage.ts bulk-delete namespace-name key1 key2 key3

Error Handling

Missing API Key

If .env file is missing or CLOUDFLARE_API_KEY is not set:

Error: CLOUDFLARE_API_KEY not found in environment

Solution: Create .env file in project root:
  echo "CLOUDFLARE_API_KEY=your_token_here" > .env

Invalid Permissions

If API token lacks required permissions:

Error: Insufficient permissions for Workers deployment

Required: Workers Scripts: Edit
Current: Workers Scripts: Read

Solution: Update token permissions at:
  https://dash.cloudflare.com/profile/api-tokens

API Rate Limiting

If too many requests are made:

Error: Rate limit exceeded (429)

Solution: Retry automatically with exponential backoff (3 attempts)

Network Issues

If API is unreachable:

Error: Failed to connect to Cloudflare API

Solution: Check internet connection and retry

Best Practices

Security :

Never commit .env files - always add to .gitignore
Use token-based authentication (not API keys)
Rotate tokens periodically (every 90 days recommended)
Use least-privilege principle: only grant required permissions
Store secrets via Wrangler CLI: wrangler secret put SECRET_NAME

Performance :

Deploy workers to minimize latency (they run at Cloudflare edge)
Use KV storage for frequently-read data (not frequently-written)
Use R2 for large files (KV has 25MB limit per key)
Enable caching with appropriate TTLs
Keep worker scripts under 1MB for faster cold starts

Development Workflow :

Test locally first: wrangler dev for local testing
Use staging environment before production
Validate credentials after token updates: bun scripts/validate-api-key.ts
Monitor worker logs: wrangler tail worker-name
Version your workers: use names like api-v1, api-v2

Naming Conventions :

Workers: Use descriptive names (e.g., user-auth-worker not worker1)
KV namespaces: Include purpose (e.g., app-sessions, api-cache)
R2 buckets: Use lowercase with hyphens (e.g., media-assets-prod)
Be consistent across your infrastructure

Resource Management :

Delete unused workers, namespaces, and buckets
Monitor usage in Cloudflare dashboard
Free tier limits: 100,000 requests/day for Workers
Set up billing alerts to avoid surprises

Advanced Usage

For advanced scenarios including:

Complex routing configurations
Multi-region deployments
Custom domain setup
Worker-to-worker communication
Durable Objects integration
Bulk operations and migrations

See examples.md for comprehensive examples and patterns.

Script Reference

All scripts are located in ~/.claude/skills/cloudflare-manager/scripts/:

validate-api-key.ts : Validate API credentials and display permissions
workers.ts : Deploy, update, and manage Workers
kv-storage.ts : Create and manage KV namespaces and key-value pairs
r2-storage.ts : Create and manage R2 buckets and objects
pages.ts : Deploy and configure Cloudflare Pages projects
dns-routes.ts : Configure DNS records and worker routes
utils.ts : Shared utilities for API calls and error handling

Templates

Starter templates are available in ~/.claude/skills/cloudflare-manager/templates/:

worker-template.js : Basic worker template with fetch handler
wrangler.toml.template : Wrangler configuration template

Troubleshooting

Common Issues and Solutions

Issue : "Worker deployment failed with unknown error"

Symptoms : Deployment command exits with error code 1, no specific error message

Solutions :

Check script syntax: node --check ./worker.js
Verify file exists: ls -lh ./worker.js
Re-validate API key: bun scripts/validate-api-key.ts --no-cache
Check worker name is valid (alphanumeric, hyphens, underscores only)

Issue : "KV namespace not found"

Symptoms : Error when trying to read/write to namespace

Solutions :

List all namespaces: bun scripts/kv-storage.ts list-namespaces
Verify you're using namespace ID (not name) in commands
Check namespace wasn't deleted
Ensure API token has KV Storage permissions

Issue : "R2 bucket already exists" or "Bucket name taken"

Symptoms : Cannot create bucket with chosen name

Solutions :

Bucket names must be globally unique across all Cloudflare accounts
Try a more specific name: my-app-media-2024 instead of media
Use existing bucket: bun scripts/r2-storage.ts list-buckets
Names must be 3-63 characters, lowercase letters/numbers/hyphens only

Issue : "Pages deployment timeout" or "Deployment pending"

Symptoms : Deployment doesn't complete, stays in pending state

Solutions :

Check deployment status: bun scripts/pages.ts list-deployments project-name
View in dashboard: https://dash.cloudflare.com/pages
Large deployments (>1000 files) may take 5-10 minutes
Cancel and retry if stuck: Delete project and recreate

Issue : "DNS record creation failed"

Symptoms : Cannot create DNS records or routes

Solutions :

Verify zone exists: bun scripts/dns-routes.ts list-zones
Ensure domain is added to Cloudflare and active
Check nameservers point to Cloudflare: dig NS yourdomain.com
Verify API token has Zone > DNS > Edit permission

Issue : "API rate limit exceeded (429)"

Symptoms : Commands fail with "Too many requests"

Solutions :

Scripts automatically retry with exponential backoff
Wait 1-2 minutes before retrying manually
Reduce concurrent operations
Rate limits: 1200 requests per 5 minutes

Issue : "CLOUDFLARE_API_KEY not found in environment"

Symptoms : Commands fail immediately with environment error

Solutions :

Create .env file in project root (not skill directory)
Verify file content: cat .env | grep CLOUDFLARE_API_KEY
Ensure no extra spaces: CLOUDFLARE_API_KEY=token (no spaces around =)
Run commands from project root where .env exists

Quick Fix :

cd /path/to/your/project
echo "CLOUDFLARE_API_KEY=your_token_here" > .env
bun scripts/validate-api-key.ts

Security Notes

API keys are never logged or displayed in output
All API requests use HTTPS
User inputs are validated before API calls
Destructive operations (delete) require confirmation
Permissions are cached for 24 hours to minimize token exposure

Additional Resources

Cloudflare API Documentation: https://developers.cloudflare.com/api/
Workers Documentation: https://developers.cloudflare.com/workers/
KV Storage Guide: https://developers.cloudflare.com/kv/
R2 Storage Guide: https://developers.cloudflare.com/r2/
Pages Documentation: https://developers.cloudflare.com/pages/

Weekly Installs

Repository

ckorhonen/claude-skills

GitHub Stars

First Seen

Jan 1, 1970

Security Audits

Gen Agent Trust HubWarn SocketPass SnykPass

Cloudflare Manager技能：一站式管理Workers、KV、R2、Pages和DNS

🇨🇳中文介绍

Cloudflare Manager

初始设置

相关 Skills

当前 API 权限

快速入门指南

部署 Worker 容器

创建和使用 KV 存储

创建 R2 存储桶并上传文件

部署到 Cloudflare Pages

配置 DNS 和路由

常见工作流程

多服务设置

更新 Worker 配置

批量 KV 操作

错误处理

缺少 API 密钥

权限无效

API 速率限制

网络问题

最佳实践

高级用法

脚本参考

模板

故障排除

常见问题和解决方案

安全说明

其他资源

🇺🇸English

Cloudflare Manager

Initial Setup

Current API Permissions

Quick Start Guide

Deploy a Worker Container

Create and Use KV Storage

Create R2 Bucket and Upload Files

Deploy to Cloudflare Pages

Configure DNS and Routes

Common Workflows

Multi-Service Setup

Update Worker Configuration

Bulk KV Operations

Error Handling

Missing API Key

Invalid Permissions

API Rate Limiting

Network Issues

Best Practices

Advanced Usage

Script Reference

Templates

Troubleshooting

Common Issues and Solutions

Security Notes

Additional Resources

最新 Skills