cloudflare-ops

Use when the user asks to deploy an AutoHub-style project to Cloudflare, run Pages or Worker preflights, operate D1 migrations/sync, manage the local Cloudflare tunnel helper, standardize repo-local Cloudflare hacks, or add a simple DNS TXT/CNAME on a VGP zone (e.g. wpfusion.com Wordfence wfvendor=… verification). Assume CLOUDFLARE_API_TOKEN + ACCOUNT_ID are already in the shell / System Configuration secrets — do not ask Jack to paste Wrangler creds.

cloudflarepagesd1 house featured

install · efd09da

# CLI (primary)

$ autovault add jack-arturo/skillissue@efd09da503770bce1de134fc485f62e65f1d38c3:skills/cloudflare-ops/SKILL.md --sync-profiles

# MCP tool call

add_skill({ source: "github", identifier: "jack-arturo/skillissue@efd09da503770bce1de134fc485f62e65f1d38c3:skills/cloudflare-ops/SKILL.md" })

→ vault validates · signs · syncs agent skill dirs

source: jack-arturo/skillissue

Why it exists

Every AutoHub-adjacent deploy was re-discovering the same wrangler gotchas. This skill is the operator runbook: one canonical deploy path, preview D1 isolation, no split-brain pages deploys.

History

1.0.0–1.0.5

Grew from Autohub deploy scripts into a signed AutoVault skill. Preview D1/KV pairs and the GitHub-connected Pages rule landed after split-brain incidents.

How Jack actually uses it

Use before any Cloudflare mutation. Prefer git push on GitHub-connected Pages. Never wrangler pages deploy against those projects.

What it is not

Not a generic tutorial. It's the house runbook for this machine and these agents.

cloudflare-lead-capture cloudflare-commerce-deploy

Package

Version 1.0.5 · install pin efd09da · SSOT skills/cloudflare-ops/ on GitHub · agents: claude-code, codex, autojack, cursor