cloudflare-worker-base
Set up Cloudflare Workers with Hono routing, Vite plugin, and Static Assets. Prevents 10 errors including export syntax, routing conflicts, Vite 8 nodejs_compat, base option regression, and cache corruption. Use when: creating Workers projects, configuring Hono/Vite, or troubleshooting export syntax, API route conflicts, HMR issues, or Vite 8+ compatibility.
Install with Tessl CLI
npx tessl i github:jezweb/claude-skills --skill cloudflare-worker-base87
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation 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 provides specific capabilities, includes an explicit 'Use when' clause with natural trigger terms, and targets a distinct technology stack that minimizes conflict risk. The description uses proper third-person voice and balances conciseness with comprehensive coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Set up Cloudflare Workers with Hono routing, Vite plugin, and Static Assets' and explicitly names 10 specific errors including 'export syntax, routing conflicts, Vite 8 nodejs_compat, base option regression, and cache corruption.' | 3 / 3 |
Completeness | Clearly answers both what ('Set up Cloudflare Workers with Hono routing...') AND when with an explicit 'Use when:' clause covering creation, configuration, and troubleshooting scenarios with specific trigger terms. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Workers projects', 'Hono', 'Vite', 'export syntax', 'API route conflicts', 'HMR issues', 'Vite 8+ compatibility', 'Cloudflare Workers'. These are terms developers would naturally use when seeking help. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche targeting the specific Cloudflare Workers + Hono + Vite stack. The combination of these technologies plus specific error types (nodejs_compat, base option regression) makes it highly distinctive and unlikely to conflict with generic web development skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a highly actionable and well-structured skill that effectively documents 10 real-world issues with concrete prevention strategies. The workflow clarity is excellent with clear steps and validation checkpoints. However, the skill is verbose with time-sensitive version information scattered throughout, and the monolithic structure could benefit from splitting detailed issue documentation into referenced files.
Suggestions
Move the detailed 10 issues documentation to a separate ISSUES.md file, keeping only a summary table with links in the main skill
Consolidate version history and date references into a single 'Version Compatibility' section or separate CHANGELOG.md to reduce token overhead
Remove explanatory text that Claude already knows (e.g., 'Modern frameworks generate fingerprinted filenames') and focus on the prevention steps only
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains valuable information but is verbose in places - the extensive version history, multiple date references, and some explanatory text (e.g., explaining what gradual rollouts are) could be trimmed. The 10 documented issues section is comprehensive but could be more condensed. | 2 / 3 |
Actionability | Excellent actionability with complete, executable code examples throughout. The Quick Start section is copy-paste ready, all issue preventions include concrete code solutions, and configuration examples are complete with actual values and syntax. | 3 / 3 |
Workflow Clarity | Clear numbered steps in Quick Start with explicit validation points. The troubleshooting section includes specific commands for cache clearing and rebuilding. The /deploy command documents a clear pipeline with edge cases handled. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the skill is monolithic - all 10 issues are inline rather than referenced to a separate troubleshooting file. The templates reference is good, but the main document could benefit from splitting detailed issue documentation into a separate file. | 2 / 3 |
Total | 10 / 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.