nuxt-modules
Use when creating Nuxt modules: (1) Published npm modules (@nuxtjs/, nuxt-), (2) Local project modules (modules/ directory), (3) Runtime extensions (components, composables, plugins), (4) Server extensions (API routes, middleware), (5) Releasing/publishing modules to npm, (6) Setting up CI/CD workflows for modules. Provides defineNuxtModule patterns, Kit utilities, hooks, E2E testing, and release automation.
89
86%
Does it follow best practices?
Impact
89%
1.18xAverage score across 6 eval scenarios
Passed
No known issues
Quality
Discovery
100%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 skill description that clearly defines its scope around Nuxt module development with explicit trigger guidance and comprehensive enumeration of use cases. It uses proper third-person voice, includes highly specific technical terms that users would naturally use, and the numbered list of scenarios makes it easy for Claude to match against user requests. The description is concise yet thorough, covering both the 'what' and 'when' effectively.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: creating published npm modules, local project modules, runtime extensions (components, composables, plugins), server extensions (API routes, middleware), releasing/publishing, CI/CD workflows, defineNuxtModule patterns, Kit utilities, hooks, E2E testing, and release automation. | 3 / 3 |
Completeness | Explicitly answers both 'what' (defineNuxtModule patterns, Kit utilities, hooks, E2E testing, release automation) and 'when' (opens with 'Use when creating Nuxt modules' followed by a numbered list of six specific trigger scenarios). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Nuxt modules', '@nuxtjs/', 'nuxt-', 'modules/ directory', 'defineNuxtModule', 'Kit utilities', 'hooks', 'E2E testing', 'release automation', 'CI/CD', 'npm modules', 'composables', 'plugins', 'API routes', 'middleware'. These cover many natural variations of how users would describe Nuxt module work. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche focused specifically on Nuxt module development. The specific triggers like 'defineNuxtModule', '@nuxtjs/', 'nuxt-' prefixes, and 'Kit utilities' are unique to this domain and unlikely to conflict with general Vue, Nuxt app development, or other framework skills. | 3 / 3 |
Total | 12 / 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.
This is a well-structured skill overview that excels at progressive disclosure and conciseness, serving as an effective entry point that routes to detailed references. Its main weakness is that the SKILL.md itself provides limited actionable content beyond scaffolding commands—the core development patterns are entirely deferred to reference files (which weren't provided for evaluation). Adding a minimal defineNuxtModule example and a high-level development workflow with validation steps would strengthen it significantly.
Suggestions
Add a minimal but executable defineNuxtModule code example in the SKILL.md itself so Claude has immediate actionable guidance without needing to load reference files for basic tasks.
Add a high-level development workflow section with numbered steps and validation checkpoints (e.g., scaffold → implement → test with `npm run test` → build → publish) to clarify the end-to-end process.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It assumes Claude knows what Nuxt modules are, avoids explaining basic concepts, and every section serves a clear purpose. The module types table and project structure are compact yet informative. | 3 / 3 |
Actionability | The quick start commands are concrete and executable, and the project structure is helpful. However, the actual module development guidance (defineNuxtModule patterns, Kit utilities, hooks) is entirely deferred to reference files which aren't provided, so the SKILL.md itself lacks executable code examples for the core task. | 2 / 3 |
Workflow Clarity | The quick start provides a clear sequence for scaffolding, and the loading checklist guides which references to consult. However, there's no explicit workflow for the actual module development process (create → implement → test → validate → publish) with validation checkpoints, which is important for a multi-step skill like this. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a clear overview, well-signaled one-level-deep references to three specific files, a task-based loading checklist, and an explicit instruction not to load all files at once. The navigation is intuitive and appropriately structured. | 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
- popey/nuxt-skills
- Commit
6b12458
- 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.