bun-nuxt

Use when running Nuxt 3 with Bun runtime, building Vue/Nuxt apps with Bun, or configuring Nuxt projects to use Bun for development and production.

Quality

70%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/bun/skills/bun-nuxt/SKILL.md

Quality

Discovery

89%

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 solid description with clear trigger guidance and a well-defined niche. Its main weakness is that the 'what' portion could be more specific about the concrete actions the skill enables (e.g., resolving Bun compatibility issues, configuring package.json scripts, handling Bun-specific module resolution). The trigger terms and completeness are strong.

Suggestions

Add more specific concrete actions like 'resolve Bun compatibility issues, configure bun-specific scripts, handle module resolution differences' to improve specificity.

Dimension	Reasoning	Score
Specificity	The description names the domain (Nuxt 3 with Bun runtime) and mentions some actions like 'building Vue/Nuxt apps' and 'configuring Nuxt projects', but doesn't list specific concrete actions like setting up bun scripts, resolving compatibility issues, or configuring nuxt.config.ts.	2 / 3
Completeness	The description explicitly answers both 'what' (running Nuxt 3 with Bun, building Vue/Nuxt apps with Bun, configuring Nuxt projects for Bun) and 'when' via the 'Use when...' clause with clear trigger scenarios.	3 / 3
Trigger Term Quality	Includes strong natural keywords users would say: 'Nuxt 3', 'Bun', 'Vue', 'Nuxt apps', 'development and production', 'configuring Nuxt projects'. These cover the main terms a user would naturally use when seeking help with this specific stack.	3 / 3
Distinctiveness Conflict Risk	The combination of 'Nuxt 3' + 'Bun runtime' is a very specific niche that is unlikely to conflict with general Vue skills, general Nuxt skills, or general Bun skills. The triggers are distinct and narrowly scoped.	3 / 3
	Total	11 / 12 Passed

Implementation

50%

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

The skill provides highly actionable, executable code examples for running Nuxt 3 with Bun, but is significantly bloated with standard Nuxt/Vue patterns that Claude already knows (useFetch, H3 event handling, composables, environment variables). The Bun-specific content — the preset configuration, bun:sqlite usage, Docker setup, and the --bun flag — is valuable but buried among generic Nuxt documentation. The skill would benefit greatly from trimming to only Bun-specific guidance and moving standard Nuxt patterns to reference files.

Suggestions

Remove sections that document standard Nuxt/Vue patterns Claude already knows (useFetch, H3 event handling, server middleware auth patterns, environment variables/runtimeConfig) — keep only Bun-specific content like the preset, bun:sqlite integration, and --bun flag usage.

Move the extensive code examples (composables, server utilities, Nitro features) into a reference file like references/bun-nuxt-examples.md and link to it from the main skill.

Add validation checkpoints to the deployment workflow, e.g., verify the build output exists before running, check that the server starts successfully, and include a health check in the Docker configuration.

Consolidate the Common Errors table to focus on Bun-specific issues rather than generic Nuxt errors like 'Hydration mismatch' and 'EADDRINUSE'.

Dimension	Reasoning	Score
Conciseness	The skill is extremely verbose at ~250+ lines, with many sections that teach standard Nuxt/Vue patterns Claude already knows (useFetch, H3 event handling, composables, server middleware, environment variables, runtimeConfig). The composables, server utilities, and Nitro features sections are largely standard Nuxt documentation rather than Bun-specific guidance.	1 / 3
Actionability	The skill provides fully executable, copy-paste ready code throughout — from project setup commands, to complete TypeScript server routes, Vue components, Docker configurations, and nuxt.config.ts examples. All code is concrete and specific.	3 / 3
Workflow Clarity	The Quick Start provides a clear sequence for project creation and the Deployment section has a clear build-then-run flow. However, there are no validation checkpoints — no steps to verify the build succeeded, no error recovery loops, and the Docker build has no health check or verification step.	2 / 3
Progressive Disclosure	The skill references external files (references/nitro.md, references/deployment.md, dependency-upgrade skill) with clear loading conditions, which is good. However, the massive amount of inline content (composables, server utilities, Nitro features, H3 event handling) should be split into reference files rather than included in the main SKILL.md, making it a monolithic document.	2 / 3
	Total	8 / 12 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: secondsky/claude-skills
Commit: 5e92b71

Reviewed: 16 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.