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.
95
93%
Does it follow best practices?
Impact
100%
1.21xAverage score across 3 eval scenarios
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 well-crafted skill description that excels across all dimensions. It clearly identifies its scope (framework integration for Cloudflare Workers), lists specific supported frameworks as natural trigger terms, explicitly states when to use it, and covers the key capabilities (routing, SSR, static assets, edge deployment). The description is concise yet comprehensive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'routing, SSR, static assets, and edge deployment' along with specific frameworks (Hono, Remix, Next.js, Astro, SvelteKit, Qwik, Nuxt). Uses third person voice appropriately. | 3 / 3 |
Completeness | Clearly 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 explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: specific framework names (Hono, Remix, Next.js, Astro, SvelteKit, Qwik, Nuxt), 'Cloudflare Workers', 'SSR', 'routing', 'edge deployment'. These are terms developers naturally use when seeking help with these frameworks. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche targeting framework integration specifically for Cloudflare Workers. The combination of specific frameworks plus the Workers platform creates a distinct scope unlikely to conflict with general web framework skills or other cloud platform skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
87%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-crafted skill that efficiently covers multiple framework integrations with excellent use of tables, decision trees, and executable code examples. The content is highly actionable and well-organized with clear progressive disclosure to framework-specific references. The main weakness is the lack of explicit validation/verification steps in the setup and deployment workflow.
Suggestions
Add a brief deployment workflow section with validation checkpoints (e.g., 'wrangler dev' to test locally, 'wrangler deploy --dry-run' before actual deployment)
Include a quick verification step after the Hono Quick Start code to confirm the setup works (e.g., 'Run `wrangler dev` and verify response at localhost:8787')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely efficient use of tokens with tables, decision trees, and code examples. No unnecessary explanations of concepts Claude already knows - jumps straight to actionable content. | 3 / 3 |
Actionability | Provides fully executable TypeScript code with proper type definitions, complete wrangler.jsonc configurations, and copy-paste ready examples for multiple frameworks and patterns. | 3 / 3 |
Workflow Clarity | While the decision tree helps with framework selection and error table aids troubleshooting, there are no explicit validation steps or feedback loops for deployment processes. Missing verification checkpoints for the setup workflow. | 2 / 3 |
Progressive Disclosure | Excellent structure with quick start overview, clear table directing to framework-specific references (one level deep), and well-organized sections. The 'When to Load References' table clearly signals when to access detailed documentation. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- secondsky/claude-skills
- Commit
90d6bd7
- 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.