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.
89
86%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly identifies its domain (framework integration on Cloudflare Workers), lists specific frameworks and capabilities, and includes an explicit 'Use when' clause with natural trigger terms. It uses proper third-person voice and is concise without being vague. The description would effectively help Claude distinguish this skill from both general Cloudflare Workers skills and general web framework skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and concepts: routing, SSR, static assets, and edge deployment. Also names specific frameworks (Hono, Remix, Next.js, Astro, SvelteKit, Qwik, Nuxt), giving a clear picture of what the skill covers. | 3 / 3 |
Completeness | Clearly answers both 'what' (framework integration for Cloudflare Workers, covering routing, SSR, static assets, edge deployment) and 'when' (explicit 'Use when building with Hono, Remix, Next.js, Astro, SvelteKit, Qwik, or Nuxt on Workers'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: specific framework names (Hono, Remix, Next.js, Astro, SvelteKit, Qwik, Nuxt), 'Cloudflare Workers', 'routing', 'SSR', 'static assets', 'edge deployment'. These are all terms developers naturally use when seeking help with framework integration on Workers. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive by scoping to a specific niche: framework integration specifically on Cloudflare Workers. The combination of named frameworks plus the Workers platform creates a clear, non-overlapping domain that is unlikely to conflict with general web framework skills or general Cloudflare skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill that effectively serves as a hub for multiple framework integrations on Cloudflare Workers. Its strengths are the actionable code examples (especially the Hono quick start and cross-framework bindings comparison) and excellent progressive disclosure via framework-specific references. Weaknesses include missing validation/deployment verification steps and some content that could be trimmed (decision tree, generic performance tips).
Suggestions
Add a validation step after setup, e.g., 'Run `npx wrangler dev` and verify the app responds at localhost:8787' to improve workflow clarity.
Remove or condense the Performance Tips section and decision tree—Claude can reason about framework selection and general optimization without these generic pointers.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient with good use of tables and code examples, but includes some unnecessary content like the decision tree (Claude can reason about framework selection) and the performance tips section which is generic advice Claude already knows. The error table is useful but some entries are too generic. | 2 / 3 |
Actionability | Provides fully executable TypeScript code with complete Hono setup including wrangler.jsonc configuration, environment bindings access patterns across all frameworks, and concrete error handling. The code is copy-paste ready with proper type annotations. | 3 / 3 |
Workflow Clarity | The skill covers framework selection and setup well, but lacks explicit validation steps. There's no workflow for verifying a deployment works, no 'run wrangler dev and check' step, and no feedback loop for debugging common issues from the error table. For a multi-framework deployment skill, validation checkpoints would be important. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a clear overview/quick-start in the main file and well-signaled one-level-deep references to framework-specific files (references/hono.md, references/remix.md, etc.). The 'When to Load References' table clearly signals when to consult each reference. | 3 / 3 |
Total | 10 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- secondsky/claude-skills
- Commit
88da5ff
- 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.