bun-hono-integration
Use when building APIs with Hono framework on Bun, including routing, middleware, REST APIs, context handling, or web framework features.
85
81%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
89%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 solid description with excellent trigger terms and clear 'when' guidance. The main weakness is that it lists topic areas rather than specific concrete actions (e.g., 'create routes', 'add authentication middleware', 'define API endpoints'). The technology-specific focus (Hono + Bun) makes it highly distinctive and unlikely to conflict with other skills.
Suggestions
Replace topic nouns with concrete action phrases, e.g., 'Creates routes, configures middleware, builds REST API endpoints, handles request context' instead of listing categories like 'routing, middleware, REST APIs'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (APIs with Hono framework on Bun) and lists some actions/areas (routing, middleware, REST APIs, context handling, web framework features), but these are more like topic areas than concrete actions. It doesn't use action verbs like 'create routes', 'configure middleware', 'handle requests'. | 2 / 3 |
Completeness | Opens with an explicit 'Use when' clause that clearly answers when Claude should select this skill, and the listed topics (routing, middleware, REST APIs, context handling) implicitly convey what the skill does. Both what and when are addressed with explicit triggers. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Hono', 'Bun', 'routing', 'middleware', 'REST APIs', 'context handling', 'web framework'. These are terms developers would naturally use when seeking help with this stack. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific technology combination of Hono + Bun. This is unlikely to conflict with generic web framework skills or other API-building skills since it names a specific framework and runtime. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid reference skill for Hono on Bun with excellent actionability—nearly every section contains executable, typed code examples. The main weaknesses are moderate verbosity (some sections like Response Types and Routing could be tightened) and the lack of workflow guidance for multi-step development tasks. The progressive disclosure is well-handled with clear pointers to reference files.
Suggestions
Tighten the Response Types section—the multiple unreachable return statements are misleading; use separate route handlers or comments to show each response type individually.
Add a brief workflow for common multi-step tasks like 'adding a new validated endpoint' with validation/testing checkpoints.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with executable examples, but it's quite long and includes some patterns Claude would already know (basic HTTP methods, standard REST patterns). The response types section shows multiple unreachable return statements which adds bulk without clarity. Some sections could be consolidated. | 2 / 3 |
Actionability | Nearly all guidance is concrete, executable TypeScript code with proper imports and exports. Examples are copy-paste ready, covering routing, middleware, validation, error handling, and RPC mode with complete, runnable snippets. | 3 / 3 |
Workflow Clarity | The Quick Start section provides a clear sequence for project setup, but the rest of the skill is a reference catalog rather than a workflow. There are no validation checkpoints or feedback loops for common development tasks like debugging middleware order issues or verifying route registration. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear section headers progressing from basic to advanced topics. It appropriately references external files (references/middleware-list.md, references/openapi.md) with clear trigger conditions for when to load them. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- secondsky/claude-skills
- Commit
88da5ff
- 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.