CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nuxt-server

| Nuxt 4 server-side development with Nitro: API routes, server middleware, database integration, and backend patterns. Use when: creating server API routes, implementing server middleware, integrating databases (D1, PostgreSQL, Drizzle), handling file uploads, implementing WebSockets, or building backend logic with Nitro.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

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

A strong, executable Nuxt 4/Nitro cookbook with comprehensive copy-paste-ready examples and useful anti-pattern/troubleshooting sections. The main defects are two missing advertised reference files and a lack of validation around destructive database operations.

Suggestions

Create the missing references/database-patterns.md and references/websocket-patterns.md (or remove those entries from "When to Load References") so every advertised path resolves to a real file.

Add validation to destructive database operations — e.g., in [id].delete.ts verify the row exists (or check rows affected) before returning { success: true }, mirroring the existence check used in the update example.

Deduplicate content between the body and references/server.md — the inline handler, cookie, middleware, and error sections overlap the reference; keep only key examples inline and move the rest to server.md.

DimensionReasoningScore

Conciseness

Largely lean, code-first sections with useful one-line comments ("// Return data (automatically serialized to JSON)") and no beginner-level explanation of concepts Claude already knows. However, the directory tree and the "HTTP Method Suffixes" table repeat each other, the three CRUD handlers restate boilerplate, and the inline handler/cookie/middleware/error coverage duplicates sections that also appear in references/server.md — trimmable overhead that keeps it below anchor 5.

4 / 5

Actionability

Copy-paste-ready handlers with file-path comments cover the common cases end to end: params ("getRouterParam(event, 'id')"), query, body, headers, cookies, middleware, Drizzle CRUD, Zod validation ("createUserSchema.safeParse(body)"), and multipart uploads ("readMultipartFormData"). Only app-specific helpers like verifyToken/findUser are abstract, which is expected and explicitly framed as such, so this matches anchor 5 rather than anchor 4's "minor gaps".

5 / 5

Workflow Clarity

This is a pattern reference rather than a sequenced workflow, and the destructive DELETE example ("await db.delete(users).where(...)" followed by an unconditional "return { success: true }") performs no validation that the row existed — the rubric caps workflow_clarity at 3 for database operations without verification, which takes precedence over the reference-skill structure. The troubleshooting section gives implicit symptom→fix loops, but no explicit validate-then-proceed checkpoints, fitting anchor 3.

3 / 5

Progressive Disclosure

The "When to Load References" section signals each file with clear per-topic triggers (good anchor-4/5 signaling), but two of the three advertised files — references/database-patterns.md and references/websocket-patterns.md — do not exist in the bundle (only references/server.md is present), so navigation breaks for the database and WebSocket topics the description emphasizes. Broken paths are more than the "minor organization gaps" of anchor 4; the structure is present but fails on resolution, fitting anchor 3.

3 / 5

Total

15

/

20

Passed

Description

88%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 description with an explicit what-and-when structure and concrete, Nuxt-specific trigger phrases. Minor gaps: a few natural trigger synonyms (REST, endpoints, auth/sessions) are absent, and database triggers overlap with the related cloudflare-d1 skill.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "API routes, server middleware, database integration", "handling file uploads", "implementing WebSockets", "integrating databases (D1, PostgreSQL, Drizzle)" — that comprehensively cover the skill's scope. Only "backend patterns" is generic; per the anti-drift check this still fits the anchor-5 example's structure (multiple specific actions, comprehensive) better than anchor 4.

5 / 5

Completeness

Explicitly answers both: what ("Nuxt 4 server-side development with Nitro: API routes, server middleware, database integration, and backend patterns") and when ("Use when: creating server API routes, implementing server middleware, ... or building backend logic with Nitro") with concrete trigger phrases, matching the anchor-5 example.

5 / 5

Trigger Term Quality

Includes natural phrases users would say — "server API routes", "server middleware", "file uploads", "WebSockets", "Nitro" — but misses common variations the body actually covers, such as "authentication/sessions", "REST"/"endpoints", and "CRUD". Good coverage with a few natural terms missing matches anchor 4 rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

"Nuxt 4 server-side development with Nitro" carves a clear niche with distinct triggers, but "integrating databases (D1, PostgreSQL, Drizzle)" overlaps with the related cloudflare-d1 skill listed under Related Skills, and separation from nuxt-core/nuxt-data rests on the server-side qualifier. Mostly distinct with minor overlap risk against closely related skills fits anchor 4, not the minimal-conflict anchor 5.

4 / 5

Total

18

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (562 lines); consider splitting into references/ and linking

Warning

metadata_field

'metadata' should map string keys to string values

Warning

referenced_paths_exist

Referenced path issues: 2 possibly missing (references/database-patterns.md, references/websocket-patterns.md)

Warning

Total

13

/

16

Passed

Repository

secondsky/claude-skills

Path

plugins/nuxt-v4/skills/nuxt-server/SKILL.md

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.