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. Do NOT use for deploying to Vercel, Netlify, or Render (use their respective skills).

68

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Failed to scan

The risk profile of this skill

SKILL.md
Quality
Evals
Security

Quality

Content

78%Weight 40%Scale 1-5

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

The body is an effective router: lean, well-organized decision trees and a verified, consistently structured reference bundle behind it. Its weaknesses are modest — duplicated sandbox guidance, directory-level rather than file-level pointers, and no inline deploy example or post-deploy verification.

Suggestions

Deduplicate the escalated-sandbox guidance: keep the detailed recovery path in Troubleshooting and a one-line pointer in Prerequisites instead of stating it twice.

Point references to entry files (e.g., references/workers/README.md) rather than bare directories so navigation lands on a known starting page.

Add a minimal post-deploy verification step (e.g., curl the deployed URL or check `wrangler deployments list`) to close the workflow's feedback loop.

DimensionReasoningScore

Conciseness

The body is a lean router with no explanations of concepts Claude already knows, but the escalated-sandbox guidance ("rerun with sandbox_permissions=require_escalated") appears in both Prerequisites and Troubleshooting, and the Product Index tables partially duplicate the decision-tree mappings. Efficient overall with minor duplication that could be trimmed, matching anchor 4 rather than the every-token-earns-its-place profile of anchor 5.

4 / 5

Actionability

Provides a concrete runnable command ("npx wrangler whoami"), explicit auth options ("wrangler login", "CLOUDFLARE_API_TOKEN"), and decision trees mapping needs to specific reference directories. Minor gaps: no inline runnable deploy command example, and pointers are directory-level (e.g., "references/workers/") rather than file-level, so it sits at anchor 4 rather than fully copy-paste-ready anchor 5.

4 / 5

Workflow Clarity

Clear sequence (prerequisites -> auth validation -> product selection via decision tree -> reference loading) with an explicit pre-deploy auth checkpoint ("Verify auth before wrangler deploy") and a network-failure recovery loop (rerun with escalated permissions). Missing a post-deploy verification step keeps it at anchor 4 rather than the full feedback-loop coverage of anchor 5; validation is explicit, not implicit, so it is above anchor 3.

4 / 5

Progressive Disclosure

Verified against the actual bundle: all 60 cited reference directories exist, each with a consistent one-level-deep structure (README.md plus api/configuration/patterns/gotchas), and the direct file pointer "references/wrangler/auth.md" resolves. Decision trees plus a categorized Product Index give clear overview and easy navigation, matching anchor 5.

5 / 5

Total

17

/

20

Passed

Description

87%Weight 40%Scale 1-5

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 description: third-person voice, explicit what/when with multiple natural trigger synonyms, and an explicit exclusion clause that sharply reduces mis-trigger risk against competing deploy skills. The only softness is the vague "related platform services" tail, which slightly blunts specificity and keyword coverage.

DimensionReasoningScore

Specificity

Names several concrete actions ("deploy, host, publish, or set up") and specific products ("Workers, Pages"), but "related platform services" is an unspecified catch-all leaving minor coverage gaps. It lists more than 1-2 concrete actions (above anchor 3) but is not fully comprehensive (below anchor 5).

4 / 5

Completeness

Explicitly answers both: "Deploy applications and infrastructure to Cloudflare using Workers, Pages" (what) and "Use when the user asks to deploy, host, publish, or set up a project on Cloudflare" (when) with concrete trigger phrases. This matches the anchor-5 pattern and even adds negative boundary guidance, so it is clearly not the weaker-when of anchor 4.

5 / 5

Trigger Term Quality

"Use when the user asks to deploy, host, publish, or set up a project on Cloudflare" covers multiple natural synonyms users would say, plus product keywords (Workers, Pages). A few natural phrasings like "wrangler" or "put it online" are missing, so it sits between anchor 4 and the comprehensive coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

Clear niche (Cloudflare platform) with explicit conflict avoidance: "Do NOT use for deploying to Vercel, Netlify, or Render (use their respective skills)". Distinct triggers and an explicit exclusion list give minimal conflict risk, matching anchor 5 rather than the minor-overlap profile of anchor 4.

5 / 5

Total

18

/

20

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

CriteriaDescriptionResult

referenced_paths_exist

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

Warning

Total

15

/

16

Passed

Repository
tech-leads-club/agent-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.