cloudflare-manager
Comprehensive Cloudflare account management for deploying Workers, KV Storage, R2, Pages, DNS, and Routes. Use when deploying cloudflare services, managing worker containers, configuring KV/R2 storage, or setting up DNS/routing. Requires CLOUDFLARE_API_KEY in .env and Bun runtime with dependencies installed.
83
75%
Does it follow best practices?
Impact
96%
1.95xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/cloudflare-manager/skills/cloudflare-manager/SKILL.mdQuality
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 identifies its domain (Cloudflare account management), lists specific services it handles, provides explicit trigger guidance via a 'Use when' clause, and includes practical requirements. The description is concise yet comprehensive, with excellent trigger term coverage across Cloudflare's service ecosystem.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and services: deploying Workers, KV Storage, R2, Pages, DNS, and Routes. Also mentions specific requirements like CLOUDFLARE_API_KEY and Bun runtime. | 3 / 3 |
Completeness | Clearly answers both 'what' (comprehensive Cloudflare account management for deploying Workers, KV, R2, Pages, DNS, Routes) and 'when' (explicit 'Use when deploying cloudflare services, managing worker containers, configuring KV/R2 storage, or setting up DNS/routing'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Cloudflare', 'Workers', 'KV Storage', 'R2', 'Pages', 'DNS', 'Routes', 'deploying', 'worker containers', 'KV/R2 storage', 'DNS/routing'. Good coverage of Cloudflare-specific terminology. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche around Cloudflare services specifically. The combination of Cloudflare-specific terms (Workers, KV, R2, Pages) makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides highly actionable, executable commands covering a comprehensive set of Cloudflare services, which is its primary strength. However, it is excessively verbose—much of the content (troubleshooting, best practices, security notes, resource links) is either obvious to Claude or could be offloaded to separate files. The workflow sections lack validation checkpoints between steps for multi-service deployments.
Suggestions
Cut the file by 50%+: Remove the entire Best Practices section (Claude knows not to commit .env files and to use descriptive names), the Additional Resources links, the Security Notes, and the 'What happens' explanatory blocks.
Move the Troubleshooting section to a separate TROUBLESHOOTING.md and reference it with a single line from the main skill file.
Add explicit validation checkpoints in the Multi-Service Setup workflow (e.g., verify namespace ID was returned before proceeding to deploy worker with bindings).
Remove redundant content like the 'Example conversation' block and the 'Performance' note about deployment time—these don't help Claude execute the skill.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~350+ lines. Includes extensive troubleshooting sections with obvious solutions (check internet connection, verify file exists), best practices Claude already knows (don't commit .env files, use descriptive names), explanations of what KV eventual consistency means, and redundant 'What happens' sections. The security notes, additional resources, and many best practices add little value for Claude. | 1 / 3 |
Actionability | Provides fully executable bash commands for every operation with concrete examples including actual arguments, expected outputs, and exit codes. Commands are copy-paste ready with real script paths and realistic parameter values. | 3 / 3 |
Workflow Clarity | The Multi-Service Setup workflow has clear sequential steps, but lacks validation checkpoints between steps. For bulk KV operations (destructive), there are no validation or confirmation steps mentioned. The initial setup has a good validate step, but deployment workflows don't include verification that the deployment succeeded beyond checking exit codes. | 2 / 3 |
Progressive Disclosure | References examples.md for advanced usage (good), but the main file is monolithic with extensive inline troubleshooting, best practices, and error handling sections that could be split into separate files. The troubleshooting section alone is ~80 lines that would be better as a separate TROUBLESHOOTING.md reference. | 2 / 3 |
Total | 8 / 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
- secondsky/claude-skills
- Commit
88da5ff
- 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.