BD cloudflare-bundler-apps
Author Cloudflare Worker Bundler-compatible apps that build and preview correctly inside a space. Use this skill whenever you scaffold, modify, or deploy a project that will be built with `@cloudflare/worker-bundler` (i.e. anything served from `/space/:name/preview/:branch/`). Covers wrangler config, project layout, static asset rules, server entry conventions, npm dependency limits, and the most common cause of blank previews (JSX in browser scripts).
Author Cloudflare Worker Bundler-compatible apps that build and preview correctly inside a space.
As a process D 40/100 · Unfinished process — weak spots: result and completion, inputs and preconditions, failures and branches
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 5560 tokens (recommended < 5000); move details to references/ - note
edit-residuethe text marks something as outdated (lines 272): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 40/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 21 mutating operations with no state check
- 40Consistency. Frontmatter name (cloudflare-bundler-apps) differs from the folder (app-file-structure)
- 60Tools and files. Uses tools (web, node) that frontmatter does not declare
- 60Steps. 44 steps, 5 vague phrases
- 70Execution cost. Instruction body is 5560 tokens
- 100When it triggers. States when to use and when not to
- low The response is described with custom markup (10 tags): a typed call is more reliable
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 456: enough signal without eating the budget
- +4Structure: 17 headings
- +3Step-by-step instructions: 44 items
- +4Has examples (19 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.