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.
Install with Tessl CLI
npx tessl i github:secondsky/claude-skills --skill workers-frameworksOverall
score
92%
Does it follow best practices?
Validation for skill structure
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, and explicitly states when to use it. The technical specificity (SSR, routing, static assets, edge deployment) combined with the platform focus makes it highly distinctive.
| 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), 'Workers', 'SSR', 'routing', 'edge deployment', 'static assets'. These are terms developers naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche targeting specific frameworks on Cloudflare Workers platform. The combination of 'Cloudflare Workers' + specific framework names creates distinct triggers unlikely to conflict with general web development or other deployment 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 high-quality skill that efficiently covers framework integration for Cloudflare Workers. The decision tree, error table, and cross-framework binding patterns are particularly valuable. The main gap is the absence of deployment workflow validation steps, which would help catch configuration errors before they reach production.
Suggestions
Add a deployment workflow section with validation checkpoints (e.g., 'wrangler dev' to test locally, 'wrangler deploy --dry-run' before actual deployment)
Include a brief troubleshooting workflow: 'If deployment fails: 1. Check wrangler.jsonc syntax, 2. Verify bindings exist, 3. Check compatibility flags'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely efficient use of tokens with tables, decision trees, and code examples. No unnecessary explanations of what frameworks are or how they work - assumes Claude's competence throughout. | 3 / 3 |
Actionability | Provides fully executable code examples with complete Hono setup, wrangler.jsonc configurations, and environment binding patterns across all frameworks. The error table with specific solutions is immediately actionable. | 3 / 3 |
Workflow Clarity | While the content is well-organized with clear framework selection guidance, it lacks explicit validation steps or feedback loops for deployment. No verification steps after configuration changes or deployment commands. | 2 / 3 |
Progressive Disclosure | Excellent structure with quick start overview, clear reference table pointing to framework-specific files (one level deep), and well-signaled navigation via 'When to Load References' section and 'See Also' links. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 Passed | |
- 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.