cloudflare-temporary-deploy

Deploy a Worker live, no account, via wrangler --temporary.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./optional-skills/web-development/cloudflare-temporary-deploy/SKILL.md

Quality

Content

96%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 excellent, fully executable runbook: complete scaffolding code, pinned commands, a real parser script, explicit verification steps, and unusually good pitfall coverage (hidden flag, auth conflict, edge cache, rate limits). Its only weaknesses are mild version-requirement repetition and a body that could offload the limits/pitfalls tables to a reference file.

Suggestions

State the wrangler >= 4.102.0 requirement once in Prerequisites and reference it tersely elsewhere ("needs 4.102.0+, see Prerequisites") instead of repeating the version number in five sections.

Move the temporary-account product-limits table into a references/ file (e.g. references/product-limits.md) and keep a one-line pointer in SKILL.md to reduce always-loaded tokens.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — no basic-concept explanations and pitfalls are genuinely non-obvious operational facts — but the "4.102.0 or later" version requirement is repeated across Prerequisites, How to Run, Pitfalls, Quick Reference, and Verification, and the intro's write→deploy→verify sentence restates the When to Use section.	4 / 5
Actionability	Fully executable throughout: complete wrangler.jsonc and src/index.ts scaffolds, exact pinned commands ("npx wrangler@latest deploy --temporary", "curl -sS <live_url>"), a parser script with a documented JSON output contract, and a quick-reference table — copy-paste ready with no gaps.	5 / 5
Workflow Clarity	Six clearly sequenced steps with an explicit validation checkpoint ("Verify the deploy is actually live — do not trust the deploy log alone") plus a dedicated Verification checklist, and real feedback loops: redeploy-and-re-curl iteration, edge-cache staleness handling with cache-busting guidance, and rate-limit recovery.	5 / 5
Progressive Disclosure	The single bundle file (scripts/parse_deploy_output.py) exists, is referenced correctly with a path-resolution note, and complex output parsing is appropriately externalized; the body is well-sectioned but at ~113 lines the product-limits table and pitfalls could move to a reference file to keep SKILL.md a leaner overview.	4 / 5
	Total	18 / 20 Passed

Description

53%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.

The description is admirably concise and names a concrete, distinctive capability, but it omits any 'when to use' trigger guidance and never mentions Cloudflare or workers.dev, limiting both completeness and trigger-term coverage.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants a live Cloudflare Workers URL without account setup, or asks to 'deploy this and give me a link'."

Include the words "Cloudflare" and "workers.dev" so the description matches the most natural phrasings a user would say.

Mention the 60-minute claim window ("claimable for 60 minutes") to set expectations and further distinguish temporary from production deploys.

Dimension	Reasoning	Score
Specificity	"Deploy a Worker live" names the domain and one concrete action, with "via wrangler --temporary" specifying the mechanism, but no additional actions (claim, verify, iterate) are listed — matching the 1-2-concrete-actions anchor rather than the 'several specific actions' anchor above.	3 / 5
Completeness	The 'what' is clear (deploy a Worker to a live URL without an account), but there is no "Use when..." clause or equivalent explicit trigger guidance, which the rubric caps at 3.	3 / 5
Trigger Term Quality	"Worker", "wrangler", "deploy", "live", and "temporary" are relevant keywords, but the word "Cloudflare" itself is absent, as are natural variations like "workers.dev", "URL", or "link" — matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	"Worker" plus "wrangler --temporary" carves out a distinct niche with minimal conflict, but the omission of "Cloudflare" leaves minor overlap risk with generic deploy/hosting skills, so it is mostly distinct rather than fully so.	4 / 5
	Total	13 / 20 Passed

Validation

81%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Repository: NousResearch/hermes-agent
Path: optional-skills/web-development/cloudflare-temporary-deploy/SKILL.md
Commit: 68fa7e9

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.