cloudflare-temporary-deploy

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

Quality

71%

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

85%

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

The body is highly actionable with a clear, validated workflow and good progressive disclosure via a real bundle script. The main weakness is conciseness: length and time-sensitive version handling could be tightened or quarantined.

Dimension	Reasoning	Score
Conciseness	The body is largely lean and operationally focused with no padded concept explanations, but it runs long (~110 lines) and the version pin (4.102.0) and time-sensitive handling are not isolated in a deprecated/old-patterns section, which the conciseness guideline flags.	2 / 3
Actionability	It provides complete, copy-paste-ready artifacts (full wrangler.jsonc and src/index.ts) and exact executable commands (npx wrangler@latest deploy --temporary, curl -sS <live_url>) plus a quick-reference table, matching fully executable guidance.	3 / 3
Workflow Clarity	Six numbered steps form a clear sequence with an explicit validation checkpoint (step 4, curl-verify rather than trusting logs), a redeploy/re-curl feedback loop (step 5), and a separate verification checklist, satisfying explicit-validation-plus-feedback-loops.	3 / 3
Progressive Disclosure	The overview and steps stay inline while URL-parsing logic is correctly split into the verified one-level-deep bundle file scripts/parse_deploy_output.py, which is clearly signaled with absolute-path guidance and easy to navigate.	3 / 3
	Total	11 / 12 Passed

Description

57%

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 specific and distinctive but lacks explicit trigger guidance and the breadth of natural trigger terms. Adding a 'Use when...' clause with terms like 'live URL' or 'workers.dev link' would lift completeness and trigger quality.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when the user wants a live workers.dev link with no account setup'.

Broaden natural trigger terms to include phrases users actually say, such as 'live URL', 'link', or 'workers.dev'.

Optionally name a second concrete action (e.g. 'verify with curl') to push specificity toward multiple specific actions.

Dimension	Reasoning	Score
Specificity	Names the domain (Cloudflare Worker) and a concrete deploy action via the specific `wrangler --temporary` mechanism, but lists only one action rather than multiple concrete actions, matching the 'names domain and some actions' anchor.	2 / 3
Completeness	It clearly states what the skill does, but there is no 'Use when...' clause or explicit trigger guidance; the 'no account' phrasing only implies the use case, so per the guideline completeness is capped at 2.	2 / 3
Trigger Term Quality	Includes relevant natural terms like 'deploy' and 'Worker'/'wrangler' plus the distinctive 'no account', but omits common variations a user would say such as 'live URL', 'link', or 'workers.dev', so coverage is partial rather than broad.	2 / 3
Distinctiveness Conflict Risk	The narrow focus on throwaway `wrangler --temporary` deploys with the 'no account' marker carves out a clear niche unlikely to trigger for other deploy or Cloudflare skills.	3 / 3
	Total	9 / 12 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: 5be99b6

Reviewed: about 15 hours 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.