hono-project-starter

Scaffold a production-ready Hono 4.x API with TypeScript, Zod validation, OpenAPI generation, and multi-runtime support (Cloudflare Workers, Node.js, Bun).

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./backend-node/hono-project-starter/SKILL.md

Quality

Content

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

The body is highly actionable with comprehensive executable examples and a clear post-scaffold workflow, but it is long and fully inlined with no reference files, and time-sensitive version numbers are not isolated. Splitting advanced sections into reference files and isolating version constraints would improve both conciseness and progressive disclosure.

Suggestions

Move advanced/optional material (RPC client mode, auth middleware internals, integration notes) into reference files (e.g. references/advanced.md, references/integrations.md) and link to them from SKILL.md to improve progressive disclosure.

Isolate version requirements (Hono 4.x, Node >= 20, pnpm >= 9, Wrangler >= 3) in a dedicated prerequisites block or a 'compatibility' note rather than repeating them across the description, prerequisites, and commands, to reduce version-drift token cost.

Add explicit validation checkpoints after the build/type-check steps (e.g. 'Run pnpm tsc --noEmit; only proceed if it passes') to strengthen workflow clarity.

Dimension	Reasoning	Score
Conciseness	The ~440-line body is mostly actionable code, but repeats scaffold/entry/dev commands per runtime and carries version numbers (Hono 4.x, Node >= 20, pnpm >= 9) outside a deprecated section, which the rubric penalizes; it could be tightened.	3 / 5
Actionability	Provides fully executable, copy-paste-ready code and commands for every common case — app factory, entry points for all three runtimes, Zod-OpenAPI schemas, routes, services, and middleware.	5 / 5
Workflow Clarity	'First Steps After Scaffold' gives a clear numbered sequence with a verification checkpoint ('curl http://localhost:3000/api/health'), though explicit validation/feedback loops for the build/type-check steps are only implicit.	4 / 5
Progressive Disclosure	Sections are well-organized, but with no bundle/reference files present the entire ~440 lines are inlined; advanced material (RPC mode, auth middleware, integration notes) that belongs in one-level-deep reference files is kept inline.	3 / 5
	Total	15 / 20 Passed

Description

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

The description is specific and clearly niche-targeted with strong natural keywords, but it omits an explicit 'Use when...' trigger clause, which caps its completeness. Adding a usage-trigger sentence would raise the completeness score.

Suggestions

Add an explicit trigger clause, e.g. 'Use when scaffolding a new Hono API, starting a TypeScript backend project, or when the user mentions Hono, Cloudflare Workers APIs, or zod-openapi.'

Include natural synonyms/variations like 'Hono app', 'Hono project', or 'Hono starter' to broaden trigger-term coverage.

Consider mentioning '.ts' or 'API skeleton' phrasing users might naturally say when asking for a backend starter.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — 'Zod validation, OpenAPI generation, and multi-runtime support (Cloudflare Workers, Node.js, Bun)' — alongside the primary 'Scaffold' action, giving comprehensive coverage rather than just 1-2 actions.	5 / 5
Completeness	The 'what' is clear and concrete, but there is no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Strong domain keywords a user would naturally say (Hono, TypeScript, Zod, OpenAPI, Cloudflare Workers, Node.js, Bun), but lacks synonyms/variations like 'Hono app', 'Hono project', or 'starter'.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (Hono 4.x with named runtimes) with distinct triggers and minimal overlap risk against generic Express/Fastify starter skills.	5 / 5
	Total	17 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: achreftlili/deep-dev-skills
Path: backend-node/hono-project-starter/SKILL.md
Commit: 181fcbc

Reviewed: 5 hours 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.