CtrlK
BlogDocsLog inGet started
Tessl Logo

hono-api

Use when building or extending REST APIs with Hono + @hono/zod-openapi. Covers schema-first route declaration with createRoute, feature-grouped composable routers, a class-based service layer behind interfaces, the strategy pattern for multi-event webhooks, typed request validation, and auto-generated OpenAPI docs.

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

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

78%Scale 1-5

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

This is a strong, well-crafted skill that provides comprehensive, actionable guidance for building Hono REST APIs with schema-first patterns. Its main strengths are the executable code examples covering all major patterns and the useful quick-reference and common-mistakes tables. The primary weakness is that the content is somewhat monolithic for its breadth — the webhook strategy pattern and service layer details could be split into referenced files for better progressive disclosure, and minor validation steps could strengthen the workflow.

Suggestions

Consider splitting the webhook strategy pattern and service layer sections into separate referenced files (e.g., WEBHOOK.md, SERVICE-LAYER.md) to improve progressive disclosure and reduce the main file's length.

Add brief validation/verification steps after key workflows, such as 'verify the route appears in /openapi.json' after mounting a new router, or 'run the scaffolding script and confirm files were created' after using the bash scaffolders.

DimensionReasoningScore

Conciseness

The skill is mostly efficient and avoids explaining basic concepts Claude already knows (e.g., what Hono is, what Zod does). There are minor instances of over-explanation, such as the detailed rationale for interface-first design and some of the bullet-point elaborations that could be trimmed, but overall it respects token budget well for the breadth of topics covered.

4 / 5

Actionability

The skill provides fully executable, copy-paste ready code examples for every major pattern: route+schema, service layer with interface, webhook dispatcher with strategy pattern, app mounting, typed validation, and runtime adapters. The quick reference table and common mistakes table add concrete, specific guidance that covers the common cases thoroughly.

5 / 5

Workflow Clarity

The skill clearly sequences how to add new routes, services, and webhook strategies, with the quick reference table serving as a concise workflow guide. The 'Additional resources' section mentions scaffolding scripts with clear usage instructions. However, there are no explicit validation checkpoints (e.g., 'verify the route is accessible' or 'run tests after adding a service'), which is a minor gap — though since these aren't destructive/batch operations, the cap at 3 doesn't apply.

4 / 5

Progressive Disclosure

The content is well-structured with clear sections and headers, but it's a fairly long monolithic document (~200+ lines) that could benefit from splitting detailed patterns (webhook strategy, service layer) into separate referenced files. The 'Additional resources' section references scripts but no bundle files are provided, and there are no references to deeper documentation files for advanced topics.

3 / 5

Total

16

/

20

Passed

Description

92%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.

This is a strong skill description that clearly identifies both what the skill does and when to use it. It names a specific technology stack (Hono + @hono/zod-openapi) and enumerates concrete architectural patterns and capabilities, making it highly distinctive and easy for Claude to match against user requests. Minor improvement could come from adding a few more user-facing synonyms as trigger terms.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: schema-first route declaration with createRoute, feature-grouped composable routers, class-based service layer behind interfaces, strategy pattern for multi-event webhooks, typed request validation, and auto-generated OpenAPI docs. Comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Explicitly answers both 'what' (schema-first route declaration, composable routers, service layer, strategy pattern, typed validation, OpenAPI docs) and 'when' ('Use when building or extending REST APIs with Hono + @hono/zod-openapi'). The 'Use when' clause is concrete and specific with clear trigger conditions.

5 / 5

Trigger Term Quality

Includes strong natural keywords like 'REST APIs', 'Hono', '@hono/zod-openapi', 'webhooks', 'OpenAPI docs', 'route', 'validation'. However, it leans somewhat technical and could include more user-facing synonyms like 'API endpoints', 'API documentation', 'request/response schemas', or 'Zod schemas'.

4 / 5

Distinctiveness Conflict Risk

Highly distinctive due to the specific technology stack (Hono + @hono/zod-openapi) and the detailed architectural patterns mentioned (strategy pattern for webhooks, class-based service layer). Very unlikely to conflict with other skills given the narrow, well-defined niche.

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
whimzyLive/nightshift-ai
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.