nuxt-content

Build typed, content-driven Nuxt applications with @nuxt/content. Use when working with content.config.ts, collections, queryCollection, Markdown or MDC rendering, content databases, hooks, custom sources, search, or Content v2 migrations.

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No known issues

Quality

Content

100%

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

The body is a tight, well-structured overview with executable baseline code, explicit done-when checkpoints, and clean one-level-deep references to real bundle files. It assumes Claude's intelligence and avoids concept re-explanation.

Dimension	Reasoning	Score
Conciseness	The ~50-line body assumes Claude's competence, avoids explaining Nuxt or basic concepts, and every section (workflow, routing table, baseline code) earns its tokens, matching the 'lean and efficient' anchor.	3 / 3
Actionability	Provides copy-paste-ready 'content.config.ts' and Vue component code, a concrete 'npx nuxi typecheck' command, and a task→reference routing table — fully executable guidance rather than abstraction.	3 / 3
Workflow Clarity	The three-step workflow has explicit validation checkpoints ('The branch is understood when...', 'The change is complete when collection types resolve...') plus a typecheck command and an empty-query diagnostic hint, satisfying the top anchor.	3 / 3
Progressive Disclosure	A compact overview routes each task category to one-level-deep references (collections.md, querying.md, rendering.md, config.md, advanced.md), all verified to exist as real bundle files, with clear navigation and no nested indirection.	3 / 3
	Total	12 / 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 concise, well-targeted description that names concrete actions, provides explicit 'Use when' triggers, and is clearly distinguishable from adjacent Nuxt skills. Third-person imperative voice is used throughout with no over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities and surfaces — 'content.config.ts, collections, queryCollection, Markdown or MDC rendering, content databases, hooks, custom sources, search, or Content v2 migrations' — matching the 'multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicitly answers both 'what' ('Build typed, content-driven Nuxt applications with @nuxt/content') and 'when' via an explicit 'Use when working with...' clause, matching the top anchor.	3 / 3
Trigger Term Quality	The 'Use when working with...' clause surfaces the actual API/file names developers would naturally invoke, giving good coverage of natural trigger terms rather than generic jargon.	3 / 3
Distinctiveness Conflict Risk	Scoped tightly to @nuxt/content with triggers tied to its own APIs, and the body explicitly delegates Nuxt/Studio/UI/Vue surfaces elsewhere, making conflict with other skills unlikely.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: onmax/nuxt-skills
Commit: a212359

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.