huiferhuifer/CloudSaver/skills/cloudflare-audit/SKILL.md

cloudflare-audit

Skill2 starsChanged 5 months agoApache-2.0View on GitHub

Cloudflare platform cost optimization expert. Monitors Workers, D1, KV, R2 usage, identifies cost anomalies, and provides optimization recommendations. Trigger when user mentions Cloudflare costs, Workers optimization, or platform audit.

In this repository8 other files it gives its agents.
- cost-audit-masterSkill
- cost-monitorSkill
- d1-cost-optimizerSkill
- index-optimizerSkill
- query-rewriterSkill
- redis-auditSkill
- spend-cap-managerSkill
- supabase-auditSkill

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
Check Row Reads and query patterns.
line 38
Very specific:
Check storage usage and operation counts.
line 56

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

Cloudflare Cost Optimization Expert

Cost Components

Service	Free Tier	Billing Metric
Workers	100K req/day	Invocations
D1	5M reads/day	Row Reads
KV	100K reads/day	Operations
R2	10GB storage	Storage + Operations
Pages	500 builds/month	Builds

Audit Workflow

Step 1: Check Workers Usage

wrangler analytics

Analyze invocation patterns and CPU time. See cases/workers-optimization.md for optimization.

Step 2: Audit D1 Costs

Check Row Reads and query patterns. See d1-cost-optimizer skill for detailed analysis.

Step 3: Monitor KV Operations

wrangler kv:key list --binding=MY_KV

Identify read/write patterns. See cases/kv-optimization.md for optimization.

Step 4: Review R2 Storage

wrangler r2 bucket list

Check storage usage and operation counts. See cases/r2-optimization.md for optimization.

Matching Cases

Service	Case File	Focus
Workers	`cases/workers-optimization.md`	Invocations, CPU time
KV	`cases/kv-optimization.md`	Operations, storage
R2	`cases/r2-optimization.md`	Storage, operations

Benchmark Reference

Optimization	Before	After	Improvement
Workers caching	100K req/day	10K req/day	90%
KV batching	100K reads	20K reads	80%
R2 presigned URLs	1M ops	100K ops	90%

Output Format

## Cloudflare Cost Audit Report

### 1. Service Usage
| Service | Current | Free Tier | Status |
|---------|---------|-----------|--------|
| Workers | X req | 100K/day | X% |
| D1 | X reads | 5M/day | X% |
| KV | X ops | 100K/day | X% |
| R2 | X GB | 10GB | X% |

### 2. Cost Analysis
- Current monthly cost: $X
- Projected cost: $X

### 3. Recommendations (by priority)
1. [P0] Apply case: <case-name> → Expected savings: $X/month

### 4. Implementation
Reference: cases/<case-name>.md

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free