hono-routing
Build type-safe APIs with Hono for Cloudflare Workers, Deno, Bun, Node.js. Routing, middleware, validation (Zod/Valibot), RPC, streaming (SSE), WebSocket, security (CSRF, secureHeaders). Use when: building Hono APIs, streaming SSE, WebSocket, validation, RPC. Troubleshoot: validation hooks, RPC types, middleware chains, JWT verify algorithm required (v4.11.4+), body consumed errors.
90
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 strong skill description that excels across all dimensions. It provides specific capabilities, comprehensive trigger terms covering the Hono ecosystem, explicit 'Use when' guidance with troubleshooting scenarios, and clear distinctiveness through framework-specific terminology. The inclusion of version-specific issues (v4.11.4+) adds practical value for debugging contexts.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: routing, middleware, validation with specific libraries (Zod/Valibot), RPC, streaming (SSE), WebSocket, security features (CSRF, secureHeaders). Also mentions specific runtimes (Cloudflare Workers, Deno, Bun, Node.js). | 3 / 3 |
Completeness | Clearly answers both what (build type-safe APIs with specific features) AND when (explicit 'Use when:' clause listing trigger scenarios plus troubleshooting contexts like 'validation hooks, RPC types, middleware chains, JWT verify algorithm'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Hono', 'APIs', 'Cloudflare Workers', 'Deno', 'Bun', 'Node.js', 'SSE', 'WebSocket', 'validation', 'Zod', 'Valibot', 'RPC', 'JWT', 'middleware'. Includes both framework names and common feature keywords. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche - specifically targets Hono framework with explicit runtime environments and Hono-specific features. Unlikely to conflict with generic API or web framework skills due to the specific framework name and associated tooling. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%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, production-ready skill with excellent actionability and workflow clarity. The comprehensive coverage of Hono features, known issues, and concrete code examples make it immediately useful. The main weakness is some verbosity in explanatory sections that could be trimmed to respect token budget better.
Suggestions
Remove 'Why X' explanation sections (Why Hono, Why Validation, Why Group Routes, Why RPC) - Claude already understands these concepts and can infer benefits from the examples
Consolidate the 'Use Cases' bullets under streaming helpers into inline comments within the code examples to reduce token count
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | While the skill is comprehensive and well-organized, it includes some unnecessary explanations Claude already knows (e.g., 'Why Hono' benefits list, 'Why Validation' section, 'Why Group Routes'). The content could be tightened by removing these justification sections. | 2 / 3 |
Actionability | Excellent actionability with fully executable code examples throughout, specific version numbers, copy-paste ready snippets, and concrete patterns for every feature. All code is complete and runnable, not pseudocode. | 3 / 3 |
Workflow Clarity | Clear multi-step workflows with explicit validation checkpoints, especially in the 'Known Issues Prevention' section which provides error patterns and correct solutions. The middleware execution order is explicitly documented with output examples. | 3 / 3 |
Progressive Disclosure | Well-structured with clear sections, references to external files (templates/, references/), and appropriate depth at each level. The skill provides quick start, detailed guides, and points to deeper documentation without nesting references more than one level deep. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (1423 lines); consider splitting into references/ and linking | Warning |
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 | 12 / 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.