CtrlK
BlogDocsLog inGet started
Tessl Logo

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

1.18x
Quality

93%

Does it follow best practices?

Impact

89%

1.18x

Average score across 6 eval scenarios

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

87%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-organized, lean overview that excels at progressive disclosure and actionability, with real reference files and a copy-paste quick start. The main gap is workflow clarity: the quick-start sequence lacks explicit validation checkpoints and deeper workflows are only referenced, not sequenced inline.

Suggestions

Add an explicit validation/checkpoint to the Quick Start (e.g., 'After npm run dev, confirm the playground serves at localhost:3000 before editing module.ts').

Collapse the 'Available Guidance' and 'Loading Files' sections into one task-based reference index to remove the near-duplicate file listing.

For destructive/batch workflows (publishing, CI), inline a brief validate-then-proceed sequence rather than only linking the reference.

DimensionReasoningScore

Conciseness

The body is lean: copy-paste quick-start commands, compact tables, and a structure tree with no padding explaining what Nuxt or modules are. Every section earns its place; the only minor redundancy is the reference list appearing in both 'Available Guidance' and 'Loading Files'.

3 / 3

Actionability

Quick Start provides fully executable commands ('npx nuxi init -t module my-module', 'npm run dev:build') and the project-structure tree is concrete; deep patterns are appropriately deferred to real reference files.

3 / 3

Workflow Clarity

Quick Start gives a clear init→install→dev/test sequence, but there are no explicit validation checkpoints or feedback loops, and the build/test/publish workflows are only pointed at via references without inline sequencing.

2 / 3

Progressive Disclosure

Clear overview with one-level-deep references; all three referenced files (development.md, testing-and-publishing.md, ci-workflows.md) exist, are well-signaled, and the 'DO NOT load all files at once' guidance supports selective loading.

3 / 3

Total

11

/

12

Passed

Description

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.

A strong, specific description that names concrete capabilities and gives an explicit 'Use when' trigger covering six scenarios. It is concise, uses natural trigger terms, and is clearly distinct from sibling Nuxt/Vue skills.

DimensionReasoningScore

Specificity

Lists many concrete actions across six enumerated module scenarios plus 'defineNuxtModule patterns, Kit utilities, hooks, E2E testing, and release automation', matching the multiple-specific-actions anchor.

3 / 3

Completeness

Explicitly answers both what ('Provides defineNuxtModule patterns, Kit utilities, hooks, E2E testing, and release automation') and when ('Use when creating Nuxt modules: ...') with an explicit trigger clause.

3 / 3

Trigger Term Quality

Natural terms a user would say are well covered: 'Nuxt modules', '@nuxtjs/', 'nuxt-', 'publishing modules to npm', and 'CI/CD workflows for modules'.

3 / 3

Distinctiveness Conflict Risk

Scoped narrowly to Nuxt module development with distinct triggers unlikely to fire for general Nuxt or Vue work.

3 / 3

Total

12

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
onmax/nuxt-skills
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.