cloudflare-deploy
Deploy applications and infrastructure to Cloudflare using Workers, Pages, and related platform services. Use when the user asks to deploy, host, publish, or set up a project on Cloudflare.
85
81%
Does it follow best practices?
Impact
89%
1.34xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
89%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 solid skill description that clearly identifies its domain (Cloudflare deployment), includes an explicit 'Use when' clause with natural trigger terms, and is distinctly scoped to avoid conflicts. The main weakness is that the 'what' portion could be more specific about the concrete actions performed beyond the general 'deploy applications and infrastructure'.
Suggestions
Expand the capabilities list with more specific actions, e.g., 'configure Workers routes, set up KV storage, manage wrangler.toml, deploy static sites via Pages, bind D1 databases'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Cloudflare deployment) and mentions specific services (Workers, Pages), but doesn't list concrete actions beyond 'deploy applications and infrastructure'. It could be more specific about what actions it performs (e.g., configure routes, set up KV bindings, manage wrangler.toml). | 2 / 3 |
Completeness | Clearly answers both 'what' (deploy applications and infrastructure to Cloudflare using Workers, Pages, and related platform services) and 'when' (explicit 'Use when' clause with trigger scenarios like deploy, host, publish, or set up on Cloudflare). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'deploy', 'host', 'publish', 'set up', 'Cloudflare', 'Workers', 'Pages'. These are terms users would naturally use when requesting Cloudflare deployment help. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to Cloudflare-specific deployment, which is a distinct niche. The mention of Workers and Pages makes it unlikely to conflict with generic deployment skills or other cloud provider skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
72%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 navigation/routing skill that efficiently directs Claude to the right Cloudflare product and reference material. Its strengths are exceptional progressive disclosure and concise decision trees. Its weaknesses are the lack of concrete deployment examples in the body and missing validation/verification steps in the deployment workflow.
Suggestions
Add a minimal end-to-end deployment example (e.g., a simple Workers deploy with `wrangler deploy`) to make the skill more immediately actionable without requiring reference file lookups.
Add a post-deployment verification step (e.g., `curl <deployed-url>` or checking wrangler output for success) to create a proper feedback loop for the deployment workflow.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. Decision trees are a compact way to convey routing logic, tables are dense, and there's no unnecessary explanation of what Cloudflare products are or how they work. Every section earns its place. | 3 / 3 |
Actionability | The authentication section provides a concrete command (`npx wrangler whoami`) and clear next steps, but the skill is primarily a routing/navigation document that delegates all actual deployment instructions to reference files. There are no executable deployment examples or copy-paste-ready deploy commands in the body itself. | 2 / 3 |
Workflow Clarity | The skill provides a clear sequence for authentication verification and decision-tree routing, but lacks an explicit end-to-end deployment workflow with validation checkpoints. There's no feedback loop for deployment failures beyond the troubleshooting section on network access, and no verification step after deployment (e.g., checking the deployed URL). | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure structure: a concise overview with decision trees for quick routing, followed by well-organized product index tables with clear one-level-deep references to specific product directories. Navigation is intuitive and references are clearly signaled. | 3 / 3 |
Total | 10 / 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
- openai/skills
- Commit
b0401f0
- 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.