Troubleshoot Cloudflare with Evidence, Not Guesses

Where this fits

A developer is chasing ERR_TOO_MANY_REDIRECTS on a production site. They suspect Cloudflare, but they aren't sure whether it's a Page Rule, a curl loop, or a misconfigured SSL mode. This skill turns that vague process into an API-driven investigation: the agent pulls the actual Cloudflare zone configuration, SSL settings, DNS records, and redirect rules before proposing any fix.

Why agents benefit

• Fetches ground truth: The agent calls the Cloudflare API to inspect live zone settings instead of guessing from partial logs or stale memory.
• Isolates failure layers: It checks DNS, SSL/TLS modes, and redirect rules separately, so the root cause emerges from evidence, not intuition.
• Handles redirect loops methodically: For ERR_TOO_MANY_REDIRECTS, the agent can enumerate every Page Rule and Bulk Redirect and test which one is bouncing the request.
• Increases trust: Every diagnosis includes the exact API response that justified the conclusion, making the agent's reasoning auditable.
• Composes with broader debugging: The skill sits on top of a general network-diagnosis methodology, so the agent doesn't start from zero on unfamiliar infrastructure.

Practical scenarios

Redirect loop on the root domain

The agent pulls all redirect rules and Page Rules for the zone, then checks the SSL/TLS encryption mode. It discovers an SSL mismatch between Cloudflare and origin that triggers a redirect loop — and tells the developer which setting to change.

SSL certificate error despite "Flexible" mode

The agent queries the edge certificate status and origin certificate details. It finds a mismatched origin certificate and pinpoints the exact hostname causing the handshake failure.

DNS resolves but traffic routes wrong

The agent lists all DNS records and compares them to the origin server IPs the developer provides. It spots a stale A record that should have been a CNAME, preventing the request from ever reaching the correct origin.

Add it to your agent workflow

Install the skill with:

npx skills add daymade/claude-code-skills --skill cloudflare-troubleshooting

Then prompt your agent with a concrete scenario:

Our site example.com throws ERR_TOO_MANY_REDIRECTS.
Domain: example.com
Cloudflare email: ops@example.com
Global API key: [scoped key]
Start the Cloudflare troubleshooting methodology.

The agent will request any missing credentials, fetch zone info, and walk through the investigation steps before recommending changes.

Compare before adopting

Before committing, compare this skill against alternatives by checking: whether it uses API evidence rather than static checklists, how recently it was updated relative to Cloudflare API changes, and whether it fits your existing debugging workflow. Also look at how it separates general network diagnostics from Cloudflare-specific logic — that modularity matters for long-term maintainability.

Why it is worth tracking

With 1,375 stars and a methodology-first approach, this skill stands out because it encodes investigation discipline instead of a handful of canned fixes. Cloudflare configuration changes frequently, so a skill that teaches the agent to read actual API responses stays relevant longer than one with hardcoded rules. For a directory entry and community signals, see this OpenAgentSkill page: https://www.openagentskill.com/skills/daymade-cloudflare-troubleshooting — and re-evaluate it whenever your own Cloudflare setup evolves.