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
Runtime module implementation patterns
Explicit #imports in composable
100%
83%
Explicit #imports in plugin/component
100%
100%
createResolver usage
100%
100%
Prefixed component name
100%
100%
Prefixed composable name
100%
100%
Server route prefix
100%
100%
consola.withTag logging
0%
12%
Error message includes tag
0%
0%
ESM imports only
100%
100%
TypeScript typed options
100%
100%
meta.compatibility set
100%
100%
addImports or addImportsDir used
100%
100%
CI/CD workflow setup for Nuxt module
Three workflow files
100%
100%
ci.yml triggers
100%
100%
ci.yml steps
62%
100%
pkg.yml uses pkg-pr-new
100%
100%
release.yml triggered by v* tag
100%
100%
release.yml waits for CI
0%
100%
Node.js 24 in release
0%
100%
id-token permission
100%
100%
npm publish --provenance
100%
100%
No NPM_TOKEN
100%
100%
pnpm used throughout
100%
100%
changelogithub for GitHub release
0%
100%
repository field requirement noted
0%
100%
Module release setup and async setup best practices
Deferred async setup
100%
100%
setup() not async
100%
100%
consola.withTag replaces console.log
0%
0%
Error message includes module tag
0%
100%
meta.compatibility added
100%
100%
bumpp added as devDependency
100%
100%
release script uses bumpp
50%
100%
Module naming convention mentioned
100%
100%
Documentation checklist in PUBLISHING.md
100%
100%
ESM-only compliance
100%
100%
runtimeConfig assignment preserved
100%
100%
repository field mentioned
100%
0%
00fb59d
Table of Contents
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.