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.

80

Quality

100%

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

100%

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

The body is a tight, concrete, well-organized reference of Hono patterns that assumes Claude's knowledge and gives actionable API-level guidance with a clear upstream-grounding workflow. It fits the simple-skill allowance for workflow clarity and progressive disclosure.

DimensionReasoningScore

Conciseness

A lean bullet list that assumes Claude's competence (e.g. references 'onion-style and order-sensitive' middleware without explaining the concept), with no padding; every token earns its place.

3 / 3

Actionability

Concrete, executable guidance throughout: specific APIs like createFactory<Env>(), c.var, c.set(), await next(), c.json(), c.env, c.executionCtx, app.request(), and testClient rather than abstract descriptions.

3 / 3

Workflow Clarity

A single-purpose patterns skill with a clear grounding decision flow (ask DeepWiki then verify locally, skip for stable basics) and explicit middleware ordering; per scoring notes, a simple well-organized skill can score 3, and no destructive/batch operation requires validation feedback loops.

3 / 3

Progressive Disclosure

No bundle files exist and the body is well under 50 lines, organized into three clearly headed sections; per the judging guideline, a short skill with no need for external references can score 3 on well-organized sections alone.

3 / 3

Total

12

/

12

Passed

Description

100%

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 precise, third-person description that names concrete capabilities and pairs them with natural user-facing trigger terms. It cleanly answers both what and when with low conflict risk.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete capabilities (API routes, middleware, request/response typing, streaming, WebSockets, Cloudflare Workers deployment), matching the anchor for listing several specific actions.

3 / 3

Completeness

It explicitly states both what it does (the capability list) and when to use it ('Use when...'), satisfying the anchor for clearly answering both what and when with explicit triggers.

3 / 3

Trigger Term Quality

'Use when users mention Hono, honojs, Cloudflare Worker handlers, Hono middleware, or Hono route typing' provides natural terms a user would actually say, with good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

Framework-specific triggers (Hono, honojs, Hono route typing) carve out a clear niche that is unlikely to fire for or conflict with other skills.

3 / 3

Total

12

/

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.

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.