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.
92
93%
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 domain-specific trigger terms that make it highly distinguishable. It follows the 'Use when...' pattern with explicit triggers and lists concrete capabilities. The description is well-structured, concise, and uses third-person voice appropriately.
| 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 trigger terms users would say: 'Nuxt modules', '@nuxtjs/', 'nuxt-', 'modules/ directory', 'components', 'composables', 'plugins', 'API routes', 'middleware', 'npm', 'CI/CD', 'defineNuxtModule', 'Kit utilities', 'hooks', 'E2E testing', 'release automation'. Good coverage of terms a Nuxt developer would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — clearly scoped to Nuxt module development specifically, with domain-specific terms like 'defineNuxtModule', '@nuxtjs/', 'Kit utilities', and 'nuxt-' prefixes that are unlikely to conflict with general Vue, Node.js, or other framework skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
87%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 that serves effectively as an overview document with strong progressive disclosure to reference files. It's concise, actionable in its quick start section, and well-organized with tables and clear navigation. The main weakness is the lack of an explicit end-to-end development workflow with validation checkpoints, which would help guide Claude through the full module creation lifecycle.
Suggestions
Add a brief numbered workflow showing the full module development lifecycle (scaffold → develop → test → validate → publish) with explicit validation checkpoints between steps.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. Every section serves a purpose—quick start commands, module types table, project structure, and references are all information Claude wouldn't inherently know about Nuxt module development. No unnecessary explanations of basic concepts. | 3 / 3 |
Actionability | The quick start section provides copy-paste ready commands. The project structure is concrete and specific. The module types table gives clear, actionable categorization. Detailed executable guidance is appropriately delegated to reference files. | 3 / 3 |
Workflow Clarity | The quick start provides a clear sequence for scaffolding a module, but there's no explicit workflow for the overall module development process (e.g., create → develop → test → validate → publish). The loading checklist helps with task routing but doesn't constitute a validated workflow with checkpoints. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a concise overview in SKILL.md and clearly signaled one-level-deep references to three specific files. The 'Loading Files' section with task-based guidance and the explicit 'DO NOT load all files at once' instruction demonstrate thoughtful content organization. | 3 / 3 |
Total | 11 / 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
3110745
- 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.