CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cloudflare-workers-frameworks

Framework integration for Cloudflare Workers. Use when building with Hono, Remix, Next.js, Astro, SvelteKit, Qwik, or Nuxt on Workers. Covers routing, SSR, static assets, and edge deployment.

65

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

68%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-structured overview skill with a genuinely useful decision tree, troubleshooting table, and executable code, backed by an actual bundle of seven framework references. Its main weakness is the absence of any validation or verification steps — nothing tells the reader to run 'wrangler dev' or confirm a deploy — and a couple of code gaps keep the quick start from being fully copy-paste ready.

Suggestions

Add a validation step after the quick start (e.g., run `wrangler dev` and hit the routes, then `wrangler deploy`) and fold the Top 10 error table into a diagnose-fix-retry loop so workflow_clarity gains explicit checkpoints.

Fix the small code gaps that break executability: define or inline the `apiHandler` used in the static-assets snippet and add the `HTTPException` import in the error-handling example.

Trim the generic Performance Tips list and the duplicated Nuxt binding snippet, and move the full Hono quick start into references/hono.md, keeping only a minimal example in the overview.

DimensionReasoningScore

Conciseness

Dense tables and executable code with essentially no concept-teaching padding. Not 5: the generic 'Performance Tips' list ('Minimize top-level code', 'Leverage Cache API and CDN') and parts of 'Common Patterns' restate knowledge Claude already has.

4 / 5

Actionability

The Hono quick start with complete wrangler.jsonc, static-assets configuration, and per-framework binding snippets is mostly copy-paste ready. Not 5: small gaps break executability — 'app.get('/api/*', apiHandler)' references an undefined handler and 'HTTPException' is used without an import.

4 / 5

Workflow Clarity

The decision tree plus the 'When to Load References' table gives a clear choose-then-load sequence, but there are no validation checkpoints anywhere — no 'wrangler dev' smoke test, no deploy verification, and no error-recovery loop despite a 10-row error table that invites one. The sequence is present but checkpoints are missing, matching anchor 3; not 4 because the gap is not minor.

3 / 5

Progressive Disclosure

Seven real one-level-deep reference files, each clearly signaled by the 'When to Load References' table, with appropriate overview content up front. Not 5: the full Hono quick start and cross-framework patterns are inlined in the overview where references/hono.md already carries per-framework detail.

4 / 5

Total

15

/

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: explicit what-and-when structure with concrete trigger phrases and a well-delineated niche. The only softness is that the headline capability 'Framework integration' is generic and some natural synonyms (deploy, edge apps) are absent.

DimensionReasoningScore

Specificity

The description names the domain ('Framework integration for Cloudflare Workers') and covers several specific areas ('routing, SSR, static assets, and edge deployment'), matching the 'several specific actions' anchor with minor gaps. It is not 3 because it goes beyond 1-2 concrete items, but not 5 because the lead phrase 'Framework integration' is a generic capability label rather than a concrete action.

4 / 5

Completeness

Explicitly answers both what ('Framework integration for Cloudflare Workers. Covers routing, SSR, static assets, and edge deployment') and when ('Use when building with Hono, Remix, Next.js, Astro, SvelteKit, Qwik, or Nuxt on Workers') with concrete trigger phrases, matching the anchor-5 pattern exactly.

5 / 5

Trigger Term Quality

Natural triggers include 'building with Hono, Remix, Next.js, Astro, SvelteKit, Qwik, or Nuxt on Workers' — framework names a user would actually say. Not 5: common synonyms like 'deploy to Cloudflare', 'edge apps', or 'wrangler' are missing.

4 / 5

Distinctiveness Conflict Risk

Clear niche (framework builds specifically on Workers) with distinct triggers (the seven framework names plus 'Workers'), so it is unlikely to fire for unrelated skills. Minor risk of overlap with generic Workers skills, but the framework names keep it distinct.

5 / 5

Total

18

/

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

secondsky/claude-skills

Path

plugins/cloudflare-workers/skills/cloudflare-workers-frameworks/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.