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.
94
92%
Does it follow best practices?
Impact
97%
1.16xAverage score across 3 eval scenarios
Risky
Do not use without reviewing
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly defines its scope (Cloudflare configuration troubleshooting), includes an explicit 'Use when' clause with specific error types as trigger terms, and differentiates itself through the API-driven investigation methodology. It uses proper third-person voice and is concise without being vague.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'investigate and resolve Cloudflare configuration issues', 'API-driven evidence gathering', 'examine actual configuration'. Also names specific error types like ERR_TOO_MANY_REDIRECTS, SSL errors, DNS issues. | 3 / 3 |
Completeness | Clearly answers both 'what' (investigate and resolve Cloudflare configuration issues using API-driven evidence gathering) and 'when' (explicit 'Use when troubleshooting ERR_TOO_MANY_REDIRECTS, SSL errors, DNS issues, or any Cloudflare-related problems'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'ERR_TOO_MANY_REDIRECTS', 'SSL errors', 'DNS issues', 'Cloudflare', 'troubleshooting', 'Cloudflare-related problems'. These are exactly the terms a user experiencing these issues would use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: Cloudflare-specific troubleshooting via API. The combination of Cloudflare + API-driven investigation + specific error types makes it very unlikely to conflict with generic networking or DNS skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, highly actionable skill with clear investigation workflows and executable API commands for common Cloudflare troubleshooting scenarios. Its main weakness is moderate verbosity—some content is repeated (the complete example largely duplicates the redirect loop section), and some best practices state things Claude already knows. The progressive disclosure and workflow clarity are excellent, with proper validation steps and external references.
Suggestions
Remove or significantly condense the 'Example: Complete Investigation' section since it largely duplicates the redirect loop pattern already covered in detail above.
Trim the 'API Usage' best practices to remove obvious guidance Claude already knows (e.g., HTTP method descriptions, 'parse JSON responses').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly long with some redundancy—the redirect loop investigation appears in both the 'Common Investigation Patterns' section and the 'Example: Complete Investigation' section. The best practices section includes some obvious guidance (e.g., 'Use appropriate methods: GET: Retrieve information') that Claude already knows. However, the API-specific curl commands and diagnosis logic earn their place. | 2 / 3 |
Actionability | The skill provides fully executable curl commands for every investigation step, with specific API endpoints, headers, and JSON payloads. The diagnosis logic sections connect evidence to conclusions, and fixes include copy-paste ready commands including cache purging. | 3 / 3 |
Workflow Clarity | The investigation methodology follows a clear numbered sequence (gather credentials → get zone ID → investigate → analyze → fix → verify). Each investigation pattern has explicit evidence-gathering steps with validation checkpoints (verify fix via API query, purge cache, re-query). The workflow template and complete example reinforce the sequence with feedback loops. | 3 / 3 |
Progressive Disclosure | The skill provides a clear overview with well-organized sections, and appropriately references external files (references/api_overview.md, references/ssl_modes.md, references/common_issues.md) for detailed information. References are one level deep and clearly signaled with descriptions of what each contains. | 3 / 3 |
Total | 11 / 12 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- fernandezbaptiste/claude-code-skills
- Commit
4f0eae8
- 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.