tessl-labs/hono-best-practices
Production Hono patterns — zValidator hooks, typed generics, error handling, middleware composition, testing, and multi-runtime deployment
87
80%
Does it follow best practices?
Impact
98%
2.57xAverage score across 5 eval scenarios
Passed
No known issues
Quality
Discovery
75%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 description effectively communicates when to use the skill with explicit trigger guidance and establishes a clear niche around Hono framework patterns. However, it focuses more on problems prevented than concrete actions performed, and could benefit from additional natural trigger terms users might use when working with Hono or similar frameworks.
Suggestions
Add more concrete actions like 'configure error handlers, validate request schemas, set up middleware chains' to improve specificity
Include additional trigger terms users might naturally say such as 'REST API', 'Cloudflare Workers', 'edge runtime', or 'TypeScript backend'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Hono API/backend) and mentions some actions ('building, extending, scaffolding') but describes patterns/problems to prevent rather than listing concrete specific actions like 'validate request bodies' or 'configure error handlers'. | 2 / 3 |
Completeness | Clearly answers both what ('Production Hono patterns that prevent untyped validation errors, leaked internals, broken middleware composition, and runtime-specific deployment bugs') and when ('Apply whenever building, extending, or scaffolding a Hono backend -- even if the task only asks for routes or CRUD endpoints'). | 3 / 3 |
Trigger Term Quality | Includes 'Hono', 'API', 'backend', 'routes', 'CRUD endpoints' which are relevant keywords, but misses common variations users might say like 'REST API', 'web server', 'HTTP handlers', or 'Cloudflare Workers'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific to Hono framework with clear niche; unlikely to conflict with generic API skills or other framework-specific skills due to explicit 'Hono' mentions and specific problem domains addressed. | 3 / 3 |
Total | 10 / 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 strong, actionable skill with excellent executable code examples and clear workflow guidance for Hono best practices. The main weaknesses are moderate verbosity in explanatory sections and a monolithic structure that could benefit from splitting into overview + detailed reference files. The content successfully covers critical production patterns with concrete, type-safe implementations.
Suggestions
Trim the 'Why This Matters From Day One' section to a brief bullet list - Claude doesn't need detailed explanations of what breaks without each pattern
Move the detailed checklist and error response format sections to separate reference files, keeping only a brief summary in the main skill
Remove redundant 'Key points' that restate what the code already demonstrates clearly (e.g., 'Always await next()' is shown in the code comment)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good code examples, but the 'Why This Matters From Day One' section explains concepts Claude likely knows (what happens without patterns) and some explanations are verbose. The checklist at the end duplicates information already covered in the patterns. | 2 / 3 |
Actionability | Excellent executable code examples throughout - all TypeScript snippets are copy-paste ready with proper imports, typed generics, and complete implementations. The validation hook, middleware, error handling, and testing patterns are all fully concrete and immediately usable. | 3 / 3 |
Workflow Clarity | Clear structure with numbered patterns, explicit key points after each code block, and a comprehensive checklist. The skill clearly sequences what must be done (declare types → group routes → add validation hooks → register middleware → add error handlers → configure entry point). | 3 / 3 |
Progressive Disclosure | The skill references external verifier files appropriately, but the main content is quite long (~350 lines) and could benefit from splitting detailed patterns into separate files. The checklist and error response format sections could be separate references rather than inline. | 2 / 3 |
Total | 10 / 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 | |
Reviewed
Table of Contents