Cloudflare Troubleshooting

This is a systematic approach to debugging Cloudflare issues using their API instead of clicking around the dashboard. When you hit redirect loops, SSL errors, or DNS problems, it walks you through gathering evidence with curl commands before making changes. The structure is solid: get zone ID, query actual configuration state, cross-reference settings that might conflict, then apply targeted fixes. It covers the common gotchas like flexible SSL mode causing redirect loops and includes investigation patterns for DNS, certificates, and origin errors. The emphasis on evidence over assumptions is right, though you'll still need to know enough about Cloudflare's architecture to ask the right questions. Useful if you troubleshoot Cloudflare setups regularly and want a methodical checklist.

skills.sh installs: 978
GitHub stars: 1.5K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add daymade/claude-code-skills --skill cloudflare-troubleshooting --agent claude-code

Installs into .claude/skills of the current project.

Files

Cloudflare Troubleshooting

Methodology base: the general evidence-driven network-diagnosis discipline (falsification, layered isolation, counter-review) lives in the debugging-network-issues skill. This skill is the Cloudflare domain layer on top of it.

Core Principle

Investigate with evidence, not assumptions. Always query Cloudflare API to examine actual configuration before diagnosing issues. The skill's value is the systematic investigation methodology, not predetermined solutions.

Investigation Methodology

1. Gather Credentials

Reuse the domain and authorized Cloudflare connection already supplied by the user or project configuration. Ask only for missing connection information: domain, account email plus Global API Key, or API Token. Keep the working authentication method; troubleshooting does not require replacing it.

Global API Key location: Cloudflare Dashboard → My Profile → API Tokens → View Global API Key