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 an excellent skill description that clearly defines its scope (Nuxt module development), enumerates six specific use cases, and includes concrete technical terms that serve as natural trigger keywords. The 'Use when...' clause is explicit and well-structured, and the description is distinctive enough to avoid conflicts with related but different skills like general Nuxt development or generic npm publishing.
| 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' with a clear 'Use when creating Nuxt modules' clause followed by six enumerated 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', 'composables', 'plugins', 'API routes', 'middleware'. These cover many natural variations of how a user would describe module-related work. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — focuses specifically on Nuxt module creation and publishing, which is a clear niche. The specific mention of defineNuxtModule, Kit utilities, @nuxtjs/ scope, and module directory patterns make it very unlikely to conflict with general Vue, Nuxt app development, or generic npm publishing 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 to deeper reference materials. Its main weakness is that the SKILL.md itself lacks any executable module code (e.g., a minimal defineNuxtModule example) and doesn't outline an end-to-end development workflow with validation steps, relying entirely on reference files for actionable guidance.
Suggestions
Add a minimal executable defineNuxtModule example in the Quick Start or a new 'Minimal Example' section so the skill is immediately actionable without loading reference files.
Add a brief numbered workflow (e.g., scaffold → define module → add runtime files → test with playground → run E2E tests → publish) with validation checkpoints to clarify the overall development process.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section is lean and purposeful. No unnecessary explanations of what Nuxt modules are or how npm works. The module types table and project structure are compact yet informative. The loading guidance is practical without being verbose. | 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 — the SKILL.md itself doesn't contain any executable code for the core task of writing a module. | 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 concise overview, clearly signaled one-level-deep references with descriptive labels, and a task-based loading checklist that explicitly tells Claude when to load each file. The 'DO NOT load all files at once' instruction is a smart constraint. | 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
- onmax/nuxt-skills
- Commit
48efc7a
- 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.