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.
Install with Tessl CLI
npx tessl i github:daymade/claude-code-skills --skill cloudflare-troubleshootingOverall
score
92%
Does it follow best practices?
Validation for skill structure
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 well-crafted skill description that excels across all dimensions. It provides specific actions, includes natural trigger terms that users would actually search for (including exact error messages), explicitly states both what the skill does and when to use it, and carves out a distinct niche around Cloudflare-specific troubleshooting. The description follows best practices by using third person voice and being concise yet comprehensive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Investigate and resolve Cloudflare configuration issues', 'API-driven evidence gathering', 'systematic investigation using Cloudflare API to examine actual configuration'. Describes a clear methodology and approach. | 3 / 3 |
Completeness | Clearly 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, or any Cloudflare-related problems'). Has explicit 'Use when' clause with specific triggers. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'ERR_TOO_MANY_REDIRECTS', 'SSL errors', 'DNS issues', 'Cloudflare-related problems', 'troubleshooting'. These are exact error messages and common phrases users would use when seeking help. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche focused specifically on Cloudflare configuration issues with distinct triggers like specific error codes and 'Cloudflare API'. Unlikely to conflict with generic debugging or other cloud provider 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 strong, well-structured skill that excels at actionability and workflow clarity. The investigation methodology is systematic with concrete API calls and clear validation steps. Minor verbosity in best practices sections and some redundant header repetition prevent a perfect conciseness score, but overall the skill effectively teaches Cloudflare troubleshooting through evidence-based investigation.
Suggestions
Consider creating a reusable variable or note for authentication headers rather than repeating them in every curl example to reduce token count
Trim the 'Best Practices' section by removing obvious guidance (e.g., 'Parse JSON responses - Use jq') that Claude already knows
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundant explanations (e.g., explaining what API tokens are, repeating authentication headers in every example). The 'Best Practices' and 'When Scripts Are Useful' sections add bulk that could be trimmed. | 2 / 3 |
Actionability | Excellent actionability with fully executable curl commands, specific API endpoints, complete authentication headers, and copy-paste ready examples. The investigation patterns provide concrete, executable guidance for each issue type. | 3 / 3 |
Workflow Clarity | Clear sequential workflows with explicit validation steps. The 'Workflow Template' provides a numbered sequence, and the 'Complete Investigation' example shows the full flow including verification and cache purging. Feedback loops are present (query → diagnose → fix → verify). | 3 / 3 |
Progressive Disclosure | Well-structured with clear navigation. References to external files (api_overview.md, ssl_modes.md, common_issues.md) are one level deep and clearly signaled. Content is appropriately split between quick-start patterns and detailed reference materials. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
88%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 14 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
Total | 14 / 16 Passed | |
- 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.