bun-hono-integration

Use when building APIs with Hono framework on Bun, including routing, middleware, REST APIs, context handling, or web framework features.

Quality

77%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/bun/skills/bun-hono-integration/SKILL.md

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 technology-specific distinctiveness. Its main weakness is that it lists topic areas rather than concrete actions (e.g., 'build routes', 'add authentication middleware'), which makes the capabilities somewhat less specific. The explicit 'Use when' clause is well-structured and covers the right scenarios.

Suggestions

Replace topic nouns with concrete action phrases, e.g., 'Creates routes, configures middleware, builds REST endpoints, handles request context' to improve specificity.

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	Starts 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 because of the named framework and runtime.	3 / 3
	Total	11 / 12 Passed

Implementation

64%

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, actionable reference skill with comprehensive, executable code examples covering Hono's major features. Its main weaknesses are length (could be more concise by splitting detailed sections into referenced files) and lack of validation/verification steps in workflows. The referenced bundle files don't exist, which undermines the progressive disclosure strategy.

Suggestions

Split detailed sections like Built-in Middleware, RPC Mode, and Validation with Zod into separate reference files to reduce the main skill's token footprint.

Add a verification step after the Quick Start (e.g., 'Visit http://localhost:3000 — you should see "Hello Hono!"') to improve workflow clarity.

Remove or condense the Response Types section — the multiple unreachable return statements are misleading and Claude already understands HTTP response patterns.

Dimension	Reasoning	Score
Conciseness	Generally efficient with code-forward examples, but includes some redundancy (e.g., the response types example shows multiple unreachable return statements, and some patterns like basic routing are things Claude already knows well). The file is quite long for a reference skill.	2 / 3
Actionability	Fully executable, copy-paste ready code examples throughout. Every section provides concrete TypeScript code with proper imports, and the quick start gives exact shell commands to bootstrap a project.	3 / 3
Workflow Clarity	The quick start provides a clear sequence for project setup, and sections are logically ordered from basic to advanced. However, there are no validation checkpoints or feedback loops — e.g., no guidance on verifying the server is running, testing routes, or handling common setup failures.	2 / 3
Progressive Disclosure	References to `references/middleware-list.md` and `references/openapi.md` are mentioned at the bottom with clear loading conditions, which is good. However, no bundle files are provided, so these references are unverifiable. The main file itself is quite long and could benefit from splitting detailed sections (like built-in middleware, RPC mode) into separate reference files.	2 / 3
	Total	9 / 12 Passed

Validation

100%

Warnings & errors only

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: 5e92b71

Reviewed: 16 days ago

Table of Contents

Discovery Implementation Validation

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.