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.
78
72%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/bun/skills/bun-nuxt/SKILL.mdQuality
Discovery
72%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 effectively targets a clear niche (Nuxt 3 + Bun) with good trigger terms and low conflict risk. However, it reads more as a trigger clause than a full description — it lacks explicit 'what it does' content describing concrete actions or capabilities the skill provides. Adding specific actions would significantly improve it.
Suggestions
Add concrete capability statements before the 'Use when' clause, e.g., 'Configures nuxt.config.ts for Bun compatibility, resolves Bun-specific module issues, sets up dev/build/preview scripts with Bun.'
Clarify what outputs or guidance the skill provides (e.g., 'Provides configuration templates, troubleshooting steps, and performance tips for running Nuxt 3 on Bun').
| 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 has a 'Use when...' clause that covers the 'when' well, but the 'what does this do' part is weak — it describes scenarios for triggering but doesn't clearly state what concrete capabilities or outputs the skill provides (e.g., troubleshooting, configuration templates, performance optimization). | 2 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Nuxt 3', 'Bun runtime', 'Vue/Nuxt apps', 'Bun', '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, Nuxt, or Bun skills. The description clearly carves out a distinct use case. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides excellent actionability with concrete, executable examples and good progressive disclosure with clear reference pointers. However, it suffers from including substantial standard Nuxt/Nitro content (H3 event handling, useFetch patterns, middleware) that Claude already knows, diluting the Bun-specific value. The workflow could benefit from validation steps, particularly around verifying the Bun preset is active and builds succeed.
Suggestions
Remove or drastically reduce sections on standard Nuxt patterns (H3 event handling, useFetch, middleware, composables) that aren't Bun-specific — focus only on what changes when using Bun instead of Node.
Add a validation step after build to verify the Bun preset is active, e.g., checking .output/server/index.mjs or confirming bun:sqlite availability.
Consolidate the Bun-specific differentiators (--bun flag, nitro preset, bun:sqlite, Bun.file API) more prominently and trim generic Nuxt boilerplate.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes a lot of content that Claude already knows — standard Nuxt patterns (useFetch, H3 event handling, middleware, composables) and generic Vue/Nuxt boilerplate that isn't specific to Bun. The Bun-specific content (preset config, bun:sqlite, Docker with Bun, --bun flag) is valuable, but it's diluted by sections like Server Utilities, Composables, and Server Middleware that are standard Nuxt knowledge. | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste ready code throughout — bash commands, complete TypeScript files with file paths, JSON configs, Dockerfile, and environment variable examples. Every section contains concrete, runnable code rather than abstract descriptions. | 3 / 3 |
Workflow Clarity | The Quick Start provides a clear sequence for project setup, and the Deployment section has a clear build-then-run flow. However, there are no validation checkpoints — no steps to verify the Bun preset is working correctly, no troubleshooting flow for build failures, and the common errors table is reactive rather than integrated into workflows. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections progressing from Quick Start to advanced topics. The 'When to Load References' section at the end provides clear, well-signaled one-level-deep references to additional materials for specific use cases. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
100%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
88da5ff
- 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.