cloudflare-maxxinglisted

Inspect, explain, secure, and maximize a Cloudflare account from any host project through a portable read-first toolkit. Use for Cloudflare setup, account snapshots, misconfiguration or security reviews, change attribution, DNS/WAF/Pages questions, product and free-tier recommendations, or a user-approved Cloudflare change.
AbhiiGatty/cld-flare-maxxing · ★ 2 · DevOps & Infrastructure · score 68

Install: claude install-skill AbhiiGatty/cld-flare-maxxing

# Cloudflare Maxxing Run the bundled toolkit from any project without using that project's `.env`, dependencies, or source tree. Keep all credentials and generated account state under: ```text <host-project>/.cloudflare-maxxing/ ``` Resolve the runner at `scripts/cf-maxxing.mjs` relative to this `SKILL.md`. In Claude Code, the same file is available at: ```text ${CLAUDE_PLUGIN_ROOT}/skills/cloudflare-maxxing/scripts/cf-maxxing.mjs ``` Run commands with `node "<absolute-runner-path>" <command>`. The current working directory is the host project. Add `--project=<absolute-path>` only when the user names a different project. ## First use 1. Run `init`. 2. Tell the user to create Cloudflare's **Read all resources** API token at `https://dash.cloudflare.com/profile/api-tokens`. 3. Tell them to put it in `.cloudflare-maxxing/.env.cloudflare` as `CF_READ_TOKEN`. 4. Never ask them to paste a token into chat. 5. Run `setup`, then `refresh`. 6. Read `.cloudflare-maxxing/reports/latest-report.json` and summarize the findings. Do not install root dependencies for setup, snapshots, reports, diffs, or recommendations. Run `dashboard` only when the user asks to view it; that command installs the dashboard's locked dependencies inside `.cloudflare-maxxing/dashboard/`. ## Routine commands ```text init setup refresh snapshot report diff betas capabilities resolve <alias> dashboard dashboard:build where ``` Use `refresh` for "check my account", "what is misconfigured", "what change