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 conditions, specific capabilities, and distinctive terminology. It uses proper third-person voice, provides a numbered list of use cases, and includes both high-level scenarios and concrete technical details. The description effectively differentiates itself from general Nuxt or Vue development skills.
| 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' (starts with 'Use when creating Nuxt modules' followed by six numbered trigger scenarios). The 'Use when...' clause is present and detailed. | 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 workflows', 'composables', 'plugins', 'API routes', 'middleware'. These cover many natural variations of how a user would describe Nuxt module work. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to Nuxt module development specifically, with distinct triggers like 'defineNuxtModule', '@nuxtjs/', 'nuxt-' prefixes, and 'Kit utilities' that are 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 to deeper reference materials. Its main weakness is that the SKILL.md itself contains no executable module code (e.g., a minimal defineNuxtModule example), which limits actionability for someone who only reads this file. The workflow for the full module development lifecycle could also be more explicit.
Suggestions
Add a minimal inline defineNuxtModule code example (3-5 lines) so the skill file itself provides at least one executable pattern without requiring reference file loading.
Add a brief numbered workflow for the full module lifecycle (scaffold → develop → test → publish) with at least one validation checkpoint (e.g., 'run tests before publishing').
| 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 with no inline code examples, so someone reading just this file gets no executable module code. | 2 / 3 |
Workflow Clarity | The quick start provides a clear sequence for scaffolding and running a module. However, there's no workflow for the actual development process (create module → add features → test → validate → publish), and no validation checkpoints are mentioned for any multi-step process like publishing or testing. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a clear overview, well-signaled one-level-deep references to three specific files, and a helpful checklist guiding when to load each reference. The explicit instruction to not load all files at once is a nice touch for token efficiency. | 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
00fb59d
- 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.