CtrlK
BlogDocsLog inGet started
Tessl Logo

hono

Hono patterns for TypeScript API routes, middleware, request and response typing, streaming, WebSockets, and Cloudflare Workers deployment. Use when users mention Hono, honojs, Cloudflare Worker handlers, Hono middleware, or Hono route typing.

70

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 compact, well-organized patterns reference that names real Hono/Workers APIs and gives clear middleware-ordering and testing guidance. Its main weakness is the lack of a complete runnable code example illustrating how the pieces fit together.

Suggestions

Add one short copy-paste example showing a typed Hono app with createFactory<Env>(), a middleware chain in correct order, and a handler returning c.json(), to lift actionability to fully executable.

Tighten the Upstream Grounding paragraph to the essential 'ask DeepWiki a narrow question, then verify against local types/docs' to trim minor verbosity.

Optionally include a one-line CORS+auth ordering snippet to make the middleware sequencing guidance instantly executable.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, naming APIs directly rather than explaining concepts; the only mild padding is the reference-repo gloss ('TypeScript web framework for edge runtimes') and a slightly verbose Upstream Grounding paragraph.

4 / 5

Actionability

Concrete, real API references throughout (createFactory<Env>(), Env['Variables'], c.json/text/html, c.env, c.executionCtx, app.request(), testClient) give executable hooks, but there is no complete copy-paste route/handler code block tying them together.

4 / 5

Workflow Clarity

Sequencing is explicit where it matters ('Resource setup belongs before auth; auth belongs before protected routes') and testing has a checkpoint ('Test... before reaching for a network server'), though it is a patterns list rather than a fully sequenced multi-step workflow.

4 / 5

Progressive Disclosure

A short (~25 line) body with well-organized section headers and clearly signaled one-level-deep references (upstream repo links); per the under-50-lines guideline, this is well-structured with no need for bundle files.

5 / 5

Total

17

/

20

Passed

Description

92%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, third-person description that clearly states the skill's scope and gives explicit activation triggers with synonyms. The only minor gap is the absence of file-extension or ecosystem aliases that would round out the trigger list.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — 'TypeScript API routes, middleware, request and response typing, streaming, WebSockets, and Cloudflare Workers deployment' — giving comprehensive coverage of the Hono domain.

5 / 5

Completeness

Explicitly answers both 'what' (the listed Hono pattern areas) and 'when' ('Use when users mention Hono, honojs, Cloudflare Worker handlers...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong natural triggers ('Hono, honojs, Cloudflare Worker handlers, Hono middleware, or Hono route typing') including a synonym pair, but lacks file extensions or edge/hono.dev variants that would push it to comprehensive.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (the Hono framework on Cloudflare Workers) with distinct, framework-specific triggers, so overlap risk with generic web-framework skills is minimal.

5 / 5

Total

19

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
EpicenterHQ/epicenter
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.