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.
94
Does it follow best practices?
Validation for skill structure
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 follows best practices. It uses third person voice, provides a comprehensive 'Use when...' clause with six specific trigger scenarios, lists concrete technical capabilities, and includes natural keywords that developers would use. The description is both specific enough to avoid conflicts and comprehensive enough to cover the full scope of Nuxt module development.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: creating published npm modules, local project modules, runtime extensions, server extensions, releasing/publishing, and CI/CD workflows. Also mentions specific technical patterns like defineNuxtModule, Kit utilities, hooks, E2E testing, and release automation. | 3 / 3 |
Completeness | Clearly answers both what (defineNuxtModule patterns, Kit utilities, hooks, E2E testing, release automation) AND when (explicit 'Use when creating Nuxt modules' with six numbered trigger scenarios). The 'Use when...' clause is present and comprehensive. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Nuxt modules', '@nuxtjs/', 'nuxt-', 'modules/ directory', 'components', 'composables', 'plugins', 'API routes', 'middleware', 'npm', 'CI/CD'. These are terms developers would naturally use when working with Nuxt module development. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche focus on Nuxt module development specifically. The combination of Nuxt-specific terminology (@nuxtjs/, nuxt-, defineNuxtModule, Kit utilities) makes it 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-crafted skill file that exemplifies good progressive disclosure and token efficiency. It provides actionable quick-start commands and clear navigation to detailed references. The only weakness is the lack of explicit validation steps in the workflow, which would be valuable for module publishing operations.
Suggestions
Add a brief validation checkpoint in the quick start (e.g., 'Verify playground loads at localhost:3000 before proceeding')
Consider adding a minimal publish workflow with verification steps (e.g., 'npm run build && npm pack --dry-run' before actual publish)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations of what modules are or how Nuxt works. Every section serves a purpose with minimal prose. | 3 / 3 |
Actionability | Provides executable commands for scaffolding, development, and testing. The quick start is copy-paste ready, and the project structure gives concrete file locations. | 3 / 3 |
Workflow Clarity | The quick start provides a clear sequence for getting started, but lacks validation checkpoints. For module development involving build/publish operations, explicit verification steps would strengthen the workflow. | 2 / 3 |
Progressive Disclosure | Excellent structure with clear overview and well-signaled one-level-deep references. The 'Loading Files' section with checkboxes explicitly guides when to load each reference file, and includes a clear warning against loading all files at once. | 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.
- 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.