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.
Install with Tessl CLI
npx tessl i github:secondsky/claude-skills --skill cloudflare-managerOverall
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 strong skill description that clearly identifies the Cloudflare domain, lists specific services and actions, and includes an explicit 'Use when...' clause with relevant trigger scenarios. The description uses proper third-person voice and provides practical context about requirements (API key, Bun runtime) without being verbose.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'deploying Workers, KV Storage, R2, Pages, DNS, and Routes' - these are all distinct, named Cloudflare services with clear capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Comprehensive Cloudflare account management for deploying Workers, KV Storage, R2, Pages, DNS, and Routes') and when ('Use when deploying cloudflare services, managing worker containers, configuring KV/R2 storage, or setting up DNS/routing'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'Cloudflare', 'Workers', 'KV Storage', 'R2', 'Pages', 'DNS', 'Routes', 'deploying', 'worker containers', 'KV/R2 storage', 'DNS/routing'. Good coverage of service names and actions. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche focused specifically on Cloudflare services with distinct product names (Workers, KV, R2, Pages). Unlikely to conflict with other cloud provider skills due to explicit Cloudflare branding throughout. | 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 excellent workflow clarity and progressive disclosure. The main weakness is moderate verbosity - some explanatory text about what commands do and extensive best practices could be trimmed since Claude already understands these concepts. The troubleshooting section, while thorough, adds significant length.
Suggestions
Remove explanatory comments like 'What happens:' sections - Claude understands what deployment commands do
Condense the Best Practices section to bullet points without explanations (e.g., 'Never commit .env files' doesn't need 'always add to .gitignore')
Consolidate troubleshooting into a more compact table format rather than verbose issue/symptoms/solutions blocks
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some unnecessary verbosity, such as explaining what happens during deployment ('Creates new worker container', 'Deploys JavaScript/TypeScript code') and extensive best practices sections that Claude already knows. The troubleshooting section is thorough but could be more condensed. | 2 / 3 |
Actionability | Provides fully executable bash commands throughout with specific examples, clear command syntax, and copy-paste ready code blocks. Each operation has concrete commands with expected outputs and return values documented. | 3 / 3 |
Workflow Clarity | Multi-step processes are clearly sequenced with numbered steps (Initial Setup, Multi-Service Setup). Includes explicit validation steps ('Run validation to verify your API key'), error handling with specific solutions, and clear feedback loops for troubleshooting. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections progressing from setup to quick start to common workflows to advanced usage. References external files appropriately (examples.md) and keeps the main document focused on essential operations while pointing to additional resources. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
93%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 15 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
Total | 15 / 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.