CtrlK
BlogDocsLog inGet started
Tessl Logo

cloudflare-troubleshooting

Investigate and resolve Cloudflare configuration issues using API-driven evidence gathering. Use when troubleshooting ERR_TOO_MANY_REDIRECTS, SSL errors, DNS issues, or any Cloudflare-related problems. Focus on systematic investigation using Cloudflare API to examine actual configuration rather than making assumptions.

68

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-organized Cloudflare investigation skill with concrete curl-based workflows and real bundle references. The main improvements are trimming over-explained basics and adding an explicit fix-verify-retry feedback loop around the destructive purge_everything operation.

Suggestions

Remove the GET/PATCH/POST/DELETE HTTP-method primer and obvious notes like 'Cloudflare API has limits' — Claude already knows these.

Add an explicit error-recovery loop after applying fixes (verify → if still failing, re-query evidence and retry), especially around the destructive POST purge_cache with purge_everything:true.

De-duplicate the SSL mode fix and cache-purge blocks (they appear in both the Redirect Loops section and the Complete Investigation example) and push bulk endpoint listings into references/api_overview.md.

DimensionReasoningScore

Conciseness

Mostly efficient and practical, but includes over-explanation Claude already knows — the GET/PATCH/POST/DELETE HTTP-method list, 'Cloudflare API has limits', and repeated SSL fix/purge blocks — that could be tightened.

3 / 5

Actionability

Provides fully executable, copy-paste-ready curl commands with real endpoints, headers, and jq parsing, plus a complete worked example covering the common redirect-loop case.

5 / 5

Workflow Clarity

Clear sequenced workflow template and per-issue investigation steps with explicit verify checkpoints and a making-changes checklist, though an explicit error-recovery retry loop (verify-fail → re-diagnose → retry) is only weakly present.

4 / 5

Progressive Disclosure

Well-signaled one-level-deep references to references/api_overview.md, ssl_modes.md, common_issues.md and the two bundled scripts, with the actionable core kept inline; minor gap is the large inlined curl reference that could lean more on the reference files.

4 / 5

Total

16

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that clearly states capability and triggers with concrete, user-recognizable error strings. Minor gains are possible by adding a few more synonyms (5xx codes, cache) to the trigger list.

DimensionReasoningScore

Specificity

Names the Cloudflare domain and several concrete actions — 'Investigate and resolve', 'API-driven evidence gathering', 'examine actual configuration' — but stops short of enumerating the full set of resolvable issues, leaving minor coverage gaps.

4 / 5

Completeness

Explicitly answers both what ('Investigate and resolve Cloudflare configuration issues using API-driven evidence gathering') and when ('Use when troubleshooting ERR_TOO_MANY_REDIRECTS, SSL errors, DNS issues...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes strong natural trigger terms users would actually report ('ERR_TOO_MANY_REDIRECTS', 'SSL errors', 'DNS issues') plus a catch-all 'any Cloudflare-related problems', though some synonyms (e.g. 5xx/502/503/504, cache) are absent.

4 / 5

Distinctiveness Conflict Risk

The Cloudflare-specific framing and named browser error codes carve a clear niche with minimal overlap risk against other skills.

5 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
daymade/claude-code-skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.