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).
90
87%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
82%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, technically specific description that clearly identifies the technology stack and capabilities. The main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill over other API-related skills. The specificity of 'Hono 4.x' and the enumerated runtimes make it highly distinctive.
Suggestions
Add a 'Use when...' clause with trigger phrases like 'Use when the user wants to create a Hono API, build a Cloudflare Workers backend, or scaffold a TypeScript API with OpenAPI documentation'
Consider adding common user phrasings like 'edge API', 'serverless API', or 'REST API with validation' to capture more natural request variations
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and technologies: 'Scaffold a production-ready Hono 4.x API with TypeScript, Zod validation, OpenAPI generation, and multi-runtime support' with specific runtimes enumerated. | 3 / 3 |
Completeness | Clearly answers 'what does this do' (scaffold Hono API with specific features), but lacks an explicit 'Use when...' clause or equivalent trigger guidance explaining when Claude should select this skill. | 2 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'Hono', 'API', 'TypeScript', 'Zod', 'OpenAPI', 'Cloudflare Workers', 'Node.js', 'Bun' - all terms developers naturally use when seeking this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific technology stack (Hono 4.x, Zod, OpenAPI) and runtime targets - unlikely to conflict with generic API or TypeScript skills due to the precise framework and version specification. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill that provides comprehensive, actionable guidance for scaffolding Hono projects across multiple runtimes. The code examples are complete and executable, conventions are clearly stated, and the workflow is well-sequenced. The main weakness is that the content is monolithic - for a skill this comprehensive, splitting advanced patterns and integration notes into separate files would improve navigation.
Suggestions
Consider splitting advanced patterns (RPC mode, auth middleware, error handling) into a separate PATTERNS.md file with clear links from the main skill
Move Integration Notes to a separate INTEGRATIONS.md file to reduce main skill length and improve discoverability
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing executable code without explaining basic concepts Claude already knows. Every section delivers actionable information without padding or unnecessary context. | 3 / 3 |
Actionability | Fully executable code examples throughout - scaffold commands, complete TypeScript files, and copy-paste ready patterns. All code is complete and runnable, not pseudocode. | 3 / 3 |
Workflow Clarity | Clear sequenced steps in 'First Steps After Scaffold' section with numbered workflow. The scaffold commands are clearly separated by runtime, and common commands are well-organized by use case. | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear sections, but the skill is quite long (~400 lines) with all content inline. Advanced patterns like RPC mode, auth middleware, and integration notes could be split into separate reference files for better organization. | 2 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- achreftlili/deep-dev-skills
- Commit
181fcbc
- 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.