nitro

Nitro is the framework-agnostic server toolkit (powering Nuxt) for building and deploying web servers anywhere. Use when working with nitro.config, server routes/event handlers, route rules, caching, storage, tasks, websockets, or deploying to Node/Bun/Deno/Cloudflare/Vercel.

Quality

74%

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 ./skills/nitro/SKILL.md

Quality

Content

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

An efficient, well-organized overview that excels at progressive disclosure by mapping topics to verified reference files. Weaker on inline actionability and workflow clarity since it deliberately defers executable detail to the references.

Suggestions

Add one short inline code snippet (e.g., a minimal defineHandler or nitro.config.ts example) so the body is actionable without requiring a reference file for the most common task.

Move the time-sensitive 'Nitro v3 (beta), generated at 2026-06-22' note into a clearly labeled version/migration section so it does not penalize conciseness.

Add a brief 'How to use this skill' sequence (identify the task area -> consult the matching reference -> apply the pattern) to give the navigation an explicit workflow shape.

Dimension	Reasoning	Score
Conciseness	The body is a lean index of capability bullets and three topic-to-reference tables with no concept padding; the time-sensitive line 'Nitro v3 (beta), generated at 2026-06-22' sits outside a deprecated/old-patterns section, a minor inefficiency.	4 / 5
Actionability	Concrete API names are cited (defineHandler, defineCachedHandler, nitro.config.ts, NITRO_*, runTask, useDatabase, defineRouteMeta), but the body itself contains no executable code or commands — guidance is navigation to references rather than copy-paste instruction.	3 / 5
Workflow Clarity	The topic-to-reference tables provide a clear navigation path (identify topic -> open reference), but there is no multi-step workflow with validation checkpoints; acceptable for an index skill but not explicitly sequenced.	3 / 5
Progressive Disclosure	A clear overview with well-signaled one-level-deep references organized into Core/Features/Advanced tables; all 13 referenced files exist and content is appropriately split between the overview and the references.	5 / 5
	Total	15 / 20 Passed

Description

83%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, well-structured description that clearly states what Nitro does and when to use it with concrete, natural trigger terms. Slight room to sharpen the action verbs and add file-extension triggers.

Dimension	Reasoning	Score
Specificity	Names the domain and the actions 'building and deploying web servers anywhere' plus a broad enumeration of concrete capability areas (nitro.config, route rules, caching, storage, tasks, websockets, platform deploys); the actual verbs are limited, keeping it just below comprehensive.	4 / 5
Completeness	Explicitly answers both what ('framework-agnostic server toolkit ... for building and deploying web servers anywhere') and when (concrete 'Use when working with ...' trigger phrases).	5 / 5
Trigger Term Quality	'Use when working with nitro.config, server routes/event handlers, route rules, caching, storage, tasks, websockets, or deploying to Node/Bun/Deno/Cloudflare/Vercel' provides strong natural keywords a user would say, with minor gaps (no file extensions, some synonyms).	4 / 5
Distinctiveness Conflict Risk	The Nitro/Nuxt/nitro.config naming carves a clear niche with distinct triggers, though generic server terms like caching, storage, and websockets carry minor overlap risk with related server/Nuxt skills.	4 / 5
	Total	17 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: onmax/nuxt-skills
Path: skills/nitro/SKILL.md
Commit: bc438e5

Reviewed: 6 days 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.