CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cloudflare-app-bootstrap

Get a Cloudflare Workers app to a working local request by connecting its bindings, secrets, and initial data, then verifying real application behavior. Use for app setup or onboarding after the project exists; use frameworks-on-cloudflare or cf-cli to create or configure the project, and wrangler or cf-cli for isolated commands.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-crafted instruction-only skill: lean prose that assumes competence, a clear multi-phase workflow with explicit verification checkpoints, and clean progressive disclosure with a single one-level reference. The main gaps are the absence of copy-paste command examples and an explicit error-recovery loop for the verification phase.

Suggestions

Add a short error-recovery step in 'Verify the first application request' (e.g., if the route fails or type checks break, fix and re-run) to close the feedback loop.

Include one or two concrete example command sequences for the most common cases (e.g., the typical `wrangler dev` + `d1 migrations apply --local` + secret-file setup) instead of deferring all specifics to linked docs.

DimensionReasoningScore

Conciseness

Lean, dense imperative guidance with no concept explanations or padding; every sentence carries non-obvious Cloudflare-specific instruction (e.g., 'Local secrets are not installed on a deployed Worker', 'a frontend-only dev server does not establish that server bindings work'). Not 4: no passages of over-explanation could be trimmed without losing real guidance.

5 / 5

Actionability

Concrete commands are named inline (`wrangler types`, `cf workers types`, `d1 migrations apply` with explicit `--local`/`--remote`, `cf cli search`) with clear decision rules per CLI. Not 5: commands are never assembled into copy-paste runnable sequences, and many specifics (dev command, secret file formats) are deferred to linked documentation rather than given as examples.

4 / 5

Workflow Clarity

Sections form a clear sequence (inspect project → connect resources → resolve config/secrets → verify first request → report) with explicit checkpoints: 'Run the relevant existing build and type checks', 'Check the response and the intended state change, not just that a server started'. Not 5: there is no error-recovery feedback loop (what to do when the verified request fails or type checks break); not 3: validation checkpoints are explicit, not missing or implicit.

4 / 5

Progressive Disclosure

Under 50 lines with well-organized section headers, and a single clearly signaled one-level-deep reference (references/skill-feedback.md, verified to exist) that is appropriately kept out of the main flow. Version-sensitive detail is delegated to authoritative Cloudflare doc links rather than inlined. Not 4: no content is misplaced and the reference structure is clean.

5 / 5

Total

18

/

20

Passed

Description

92%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: concrete actions, explicit when-clause with scope boundaries, and explicit disambiguation from related Cloudflare skills. The only weakness is that a few natural trigger phrases users might say (e.g., getting an app running locally) are absent.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'connecting its bindings, secrets, and initial data, then verifying real application behavior' — that comprehensively cover the bootstrap task from setup to a verified working request. Not 4: there are no minor coverage gaps; the actions span the full scope of the skill.

5 / 5

Completeness

Explicitly answers both: what ('Get a Cloudflare Workers app to a working local request by connecting its bindings, secrets, and initial data, then verifying real application behavior') and when ('Use for app setup or onboarding after the project exists'), with concrete scope boundaries. Not 4: the 'when' clause is explicit and specific rather than vague or implicit.

5 / 5

Trigger Term Quality

Good natural keywords: 'Cloudflare Workers app', 'app setup', 'onboarding', 'bindings', 'secrets'. Not 5: common user phrasings like 'get my app running locally' or 'local development' are missing; not 3: coverage goes well beyond 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

Clear niche (post-creation app setup) with explicit disambiguation — 'use frameworks-on-cloudflare or cf-cli to create or configure the project, and wrangler or cf-cli for isolated commands' — minimizing conflict with sibling skills. Not 4: overlap risk is addressed by explicit delegation guidance, not just implicit distinctness.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

cloudflare/skills

Path

skills/cloudflare-app-bootstrap/SKILL.md

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.