Skip to content

cloudthinker-ai/CloudSkills / skills/connections/managing-cloudflare-workers-deep

managing-cloudflare-workers-deep

Unverified

Use when working with Cloudflare Workers Deep — deep analysis of Cloudflare Workers deployments including script inventory, route mappings, KV namespace usage, Durable Objects, cron triggers, CPU time metrics, and error rate tracking. Use for comprehensive Workers platform health checks and optimization.

Cloudflare Workers Deep Management

Comprehensive analysis of Cloudflare Workers scripts, bindings, routes, and performance.

Phase 1: Discovery

#!/bin/bash
ACCOUNT_ID="${CF_ACCOUNT_ID}"
API_TOKEN="${CF_API_TOKEN}"
BASE="https://api.cloudflare.com/client/v4"

echo "=== Workers Scripts ==="
curl -s "${BASE}/accounts/${ACCOUNT_ID}/workers/scripts" \
  -H "Authorization: Bearer ${API_TOKEN}" \
  | jq '.result[] | {id, modified_on, usage_model, compatibility_date}'

echo ""
echo "=== KV Namespaces ==="
curl -s "${BASE}/accounts/${ACCOUNT_ID}/storage/kv/namespaces" \
  -H "Authorization: Bearer ${API_TOKEN}" \
  | jq '.result[] | {id, title}'

echo ""
echo "=== Durable Object Namespaces ==="
curl -s "${BASE}/accounts/${ACCOUNT_ID}/workers/durable_objects/namespaces" \
  -H "Authorization: Bearer ${API_TOKEN}" \
  | jq '.result[] | {id, name, script, class}'

echo ""
echo "=== Worker Routes (per zone) ==="
for ZONE_ID in $(curl -s "${BASE}/zones" -H "Authorization: Bearer ${API_TOKEN}" | jq -r '.result[].id'); do
  curl -s "${BASE}/zones/${ZONE_ID}/workers/routes" \
    -H "Authorization: Bearer ${API_TOKEN}" \
    | jq -r '.result[] | "\(.pattern)\t\(.script)"'
done | head -30

Phase 2: Analysis

#!/bin/bash
ACCOUNT_ID="${CF_ACCOUNT_ID}"
API_TOKEN="${CF_API_TOKEN}"
BASE="https://api.cloudflare.com/client/v4"

echo "=== Worker CPU Time & Request Metrics (GraphQL) ==="
SINCE=$(date -u -v-7d +"%Y-%m-%dT%H:%M:%SZ" 2>/dev/null || date -u -d "7 days ago" +"%Y-%m-%dT%H:%M:%SZ")
UNTIL=$(date -u +"%Y-%m-%dT%H:%M:%SZ")

curl -s "${BASE}/graphql" \
  -H "Authorization: Bearer ${API_TOKEN}" \
  -H "Content-Type: application/json" \
  --data "{\"query\":\"{ viewer { accounts(filter:{accountTag:\\\"${ACCOUNT_ID}\\\"}) { workersInvocationsAdaptive(limit:20, filter:{datetime_gt:\\\"${SINCE}\\\", datetime_lt:\\\"${UNTIL}\\\"}, orderBy:[sum_requests_DESC]) { dimensions { scriptName } sum { requests errors subrequests } quantiles { cpuTimeP50 cpuTimeP99 } } } } }\"}" \
  | jq '.data.viewer.accounts[0].workersInvocationsAdaptive[] | {
      script: .dimensions.scriptName,
      requests: .sum.requests,
      errors: .sum.errors,
      subrequests: .sum.subrequests,
      cpu_p50_ms: .quantiles.cpuTimeP50,
      cpu_p99_ms: .quantiles.cpuTimeP99
    }'

echo ""
echo "=== Cron Triggers ==="
for SCRIPT in $(curl -s "${BASE}/accounts/${ACCOUNT_ID}/workers/scripts" -H "Authorization: Bearer ${API_TOKEN}" | jq -r '.result[].id'); do
  CRONS=$(curl -s "${BASE}/accounts/${ACCOUNT_ID}/workers/scripts/${SCRIPT}/schedules" \
    -H "Authorization: Bearer ${API_TOKEN}" | jq -r '.result[].cron // empty')
  [ -n "$CRONS" ] && echo "${SCRIPT}: ${CRONS}"
done

echo ""
echo "=== KV Key Counts ==="
for NS_ID in $(curl -s "${BASE}/accounts/${ACCOUNT_ID}/storage/kv/namespaces" -H "Authorization: Bearer ${API_TOKEN}" | jq -r '.result[].id'); do
  TITLE=$(curl -s "${BASE}/accounts/${ACCOUNT_ID}/storage/kv/namespaces" -H "Authorization: Bearer ${API_TOKEN}" | jq -r ".result[] | select(.id==\"${NS_ID}\") | .title")
  COUNT=$(curl -s "${BASE}/accounts/${ACCOUNT_ID}/storage/kv/namespaces/${NS_ID}/keys" -H "Authorization: Bearer ${API_TOKEN}" | jq '.result | length')
  echo "${TITLE}: ${COUNT} keys (first page)"
done

Output Format

WORKER HEALTH REPORT
====================
Script          Requests   Errors   Error%   CPU-P50   CPU-P99   Model
────────────────────────────────────────────────────────────────────────
my-api          125000     23       0.02%    2.1ms     18.4ms    bundled
auth-worker     89000      1200     1.35%    5.3ms     45.2ms    unbound
cron-job        168        0        0.00%    12.0ms    80.1ms    unbound

KV Namespaces: 3 | Durable Objects: 1 | Cron Triggers: 2
Routes: 5 mapped across 2 zones

Safety Rules

  • Read-only: Only use GET endpoints against the Cloudflare API
  • Never deploy or delete scripts without explicit user confirmation
  • Rate limits: Cloudflare API allows 1200 requests per 5 minutes per user
  • Token scope: Verify token has Workers Scripts:Read and Account Analytics:Read permissions

Anti-Hallucination Rules

  1. NEVER assume resource names — always discover via CLI/API in Phase 1 before referencing in Phase 2.
  2. NEVER fabricate metric names or dimensions — verify against the service documentation or --help output.
  3. NEVER mix CLI commands between service versions — confirm which version/API you are targeting.
  4. ALWAYS use the discovery → verify → analyze chain — every resource referenced must have been discovered first.
  5. ALWAYS handle empty results gracefully — an empty response is valid data, not an error to retry.

Counter-Rationalizations

ShortcutCounterWhy
"I'll skip discovery and check known resources"Always run Phase 1 discovery firstResource names change, new resources appear — assumed names cause errors
"The user only asked for a quick check"Follow the full discovery → analysis flowQuick checks miss critical issues; structured analysis catches silent failures
"Default configuration is probably fine"Audit configuration explicitlyDefaults often leave logging, security, and optimization features disabled
"Metrics aren't needed for this"Always check relevant metrics when availableAPI/CLI responses show current state; metrics reveal trends and intermittent issues
"I don't have access to that"Try the command and report the actual errorAssumed permission failures prevent useful investigation; actual errors are informative
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 318kUpdated Claude CodeCodexUnverifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 117kUpdated Claude CodeCodexUnverifiedInstall