bun-hono-integration

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

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, token-efficient Hono reference with executable code throughout. Its main weakness is progressive disclosure: two referenced files do not exist in the bundle, and a sizable middleware catalog is inlined where a one-level-deep reference would be appropriate.

Suggestions

Create the referenced files (references/middleware-list.md and references/openapi.md) or remove the 'When to Load References' section — currently the body points to bundles that do not exist.

Move the full 'Built-in Middleware' catalog into references/middleware-list.md and keep only one or two representative examples inline in SKILL.md.

Add a brief verification checkpoint to the Quick Start (e.g., confirm the dev server prints a local URL) so the setup workflow has an explicit success signal.

Dimension	Reasoning	Score
Conciseness	The body is lean and code-forward with virtually no padding — a one-line intro ('Hono is a fast, lightweight web framework optimized for Bun.') followed by executable snippets and brief inline comments; it assumes Claude's competence and avoids explaining concepts Claude already knows.	5 / 5
Actionability	Every section provides copy-paste-ready, fully executable TypeScript covering the common cases (routing, request handling, responses, middleware, Zod validation, context variables, error handling, RPC), with real imports and concrete values.	5 / 5
Workflow Clarity	The Quick Start gives a clear, ordered sequence (create, cd, install, dev) and there are no destructive or batch operations requiring validation, but the bulk of the skill is a feature catalog rather than a sequenced workflow with checkpoints, so it falls just short of the top anchor.	4 / 5
Progressive Disclosure	Sections are well-organized with clear headers, but the body references 'references/middleware-list.md' and 'references/openapi.md' that do not exist (no references/ directory), and the large built-in middleware catalog is inlined rather than split into a reference file — structure is present but references are broken and content that should be separate is inline.	3 / 5
	Total	17 / 20 Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-structured description with an explicit 'Use when' trigger, concrete capability list, and a clearly distinct niche. The only weakness is the slightly generic 'web framework features' tail and the absence of synonym variations.

Dimension	Reasoning	Score
Specificity	Names the domain ('Hono framework on Bun') and lists several concrete capability areas — 'routing, middleware, REST APIs, context handling' — but the trailing 'or web framework features' is a generic catch-all, so it stops short of comprehensive coverage.	4 / 5
Completeness	Explicitly answers both what ('building APIs with Hono framework on Bun, including routing, middleware, REST APIs, context handling') and when ('Use when building APIs with Hono framework on Bun...') with concrete trigger phrases, matching the anchor-5 pattern.	5 / 5
Trigger Term Quality	Includes natural terms users would say ('building APIs', 'Hono framework', 'Bun', 'routing', 'middleware', 'REST APIs'), but lacks synonyms or variations beyond the core names, leaving a few natural terms missing.	4 / 5
Distinctiveness Conflict Risk	The 'Hono framework on Bun' niche is specific with distinct triggers, making overlap with other web-framework skills minimal.	5 / 5
	Total	18 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 2 missing	Warning

	Total	15 / 16 Passed

Repository: secondsky/claude-skills
Path: plugins/bun/skills/bun-hono-integration/SKILL.md
Commit: ad16332

Reviewed: 12 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.