CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

80

1.34x
Quality

73%

Does it follow best practices?

Impact

89%

1.34x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./skills/.curated/cloudflare-deploy/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-architected progressive-disclosure router that cleanly points to a large, verified reference bundle. It scores lower on actionability and workflow clarity because the actual deploy commands are referenced rather than shown, and post-deploy verification is absent.

Suggestions

Add a minimal copy-paste deploy example block for the most common case (e.g. `npx wrangler deploy` and `npx wrangler pages deploy ./dist`) so the skill is actionable without loading a reference.

Add an explicit post-deploy verification checkpoint (e.g. hit the deployed URL or run `wrangler deployments status`) given deploy is an irreversible outbound operation.

Consolidate the Prerequisites bullet and the 'Escalated Network Access' troubleshooting section, which both explain the same `sandbox_permissions=require_escalated` point, to remove redundancy.

DimensionReasoningScore

Conciseness

The decision trees and product index are reasonably lean and assume Claude's competence, but the index duplicates much of the tree routing in a second table format and the Prerequisites/Troubleshooting sections overlap on the escalated-network point, so it could be tightened to remove redundancy.

2 / 3

Actionability

It gives one concrete executable command (`npx wrangler whoami`) and points to references for everything else, but the core deploy actions (the actual `wrangler deploy` / `pages deploy` invocations) are named rather than shown as copy-paste-ready examples, leaving guidance incomplete.

2 / 3

Workflow Clarity

There is a clear sequence (auth check → decision tree → load reference) and auth is a genuine validation checkpoint, but the deploy itself has no explicit validation/verification step after it runs, which is expected for a destructive outbound operation.

2 / 3

Progressive Disclosure

The body is a concise router that splits detail into ~60 one-level-deep reference directories, all clearly signaled with paths and grouped by category; spot checks confirm the referenced directories (workers, pages, kv, wrangler/auth.md) are real files, matching the level-3 anchor.

3 / 3

Total

9

/

12

Passed

Description

90%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-structured description that clearly states both the capability and explicit usage triggers in third person with natural trigger terms. Its only weakness is the generic filler phrase 'related platform services' in place of a third concrete action.

Suggestions

Replace 'and related platform services' with one or two named services (e.g., 'Durable Objects, R2, and KV') to make all listed actions concrete rather than relying on generic padding.

DimensionReasoningScore

Specificity

Names concrete actions ('Deploy applications and infrastructure', 'using Workers, Pages, and related platform services') but 'related platform services' is generic padding rather than a third specific action, so it does not reach the 'multiple specific concrete actions' level 3.

2 / 3

Completeness

Explicitly answers what ('Deploy applications and infrastructure to Cloudflare using Workers, Pages...') and when ('Use when the user asks to deploy, host, publish, or set up a project on Cloudflare'), satisfying the level-3 anchor.

3 / 3

Trigger Term Quality

Covers natural user phrasings ('deploy', 'host', 'publish', 'set up a project', 'Cloudflare') plus product names (Workers, Pages), matching the good coverage anchor.

3 / 3

Distinctiveness Conflict Risk

Scoped tightly to Cloudflare deployment with product-specific triggers, clearly distinguishable from other skills and unlikely to fire for the wrong skill.

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 deeper-than-1-level

Warning

Total

15

/

16

Passed

Repository
openai/skills
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.