Comprehensive Cloudflare account management for deploying Workers, KV Storage, R2, Pages, DNS, and Routes. Use when deploying cloudflare services, managing worker containers, configuring KV/R2 storage, or setting up DNS/routing. Requires CLOUDFLARE_API_KEY in .env and Bun runtime with dependencies installed.
94
92%
Does it follow best practices?
Impact
96%
1.95xAverage score across 3 eval scenarios
Passed
No known issues
Worker and KV storage deployment scripts
Validates credentials
0%
100%
Correct worker deploy command
0%
100%
Correct KV namespace create command
0%
100%
KV namespace before worker
100%
100%
Descriptive worker name
100%
100%
KV namespace purpose in name
100%
100%
.env.example has CLOUDFLARE_API_KEY
0%
100%
.gitignore excludes .env
100%
100%
No spaces in env assignment
100%
100%
.env not in worker code or committed
100%
100%
R2 storage and Pages deployment
R2 for image assets
0%
100%
R2 bucket naming convention
100%
100%
R2 bucket name length
100%
100%
Pages project creation via script
0%
100%
Wrangler for actual file deploy
66%
0%
Pages env var via script
0%
100%
Validates credentials
0%
100%
.gitignore excludes .env
100%
100%
README documents env variables
0%
100%
File upload command used
0%
100%
Multi-service infrastructure with bindings and secrets
KV namespace created first
50%
100%
R2 bucket created before worker
50%
100%
Worker deploy uses --kv-binding
0%
100%
Worker deploy uses --r2-binding
0%
100%
Route configured via script
0%
100%
Secret stored via wrangler
100%
100%
Validates credentials at start
0%
100%
Descriptive KV namespace name
100%
100%
R2 bucket naming convention
100%
100%
Runbook has wrangler tail
100%
100%
Runbook has versioning convention
100%
100%
90d6bd7
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.