nuxt-content
Use when working with Nuxt Content v3, markdown content, or CMS features in Nuxt - provides collections (local/remote/API sources), queryCollection API, MDC rendering, database configuration, NuxtStudio integration, hooks, i18n patterns, and LLMs integration
99
100%
Does it follow best practices?
Impact
97%
1.27xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
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 a strong skill description that clearly identifies its niche (Nuxt Content v3), lists specific capabilities, and includes an explicit 'Use when' trigger clause. The description is concise yet comprehensive, covering the key features and natural trigger terms a developer would use. It follows third-person voice conventions and would be easily distinguishable from other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and features: collections (local/remote/API sources), queryCollection API, MDC rendering, database configuration, NuxtStudio integration, hooks, i18n patterns, and LLMs integration. These are concrete, identifiable capabilities. | 3 / 3 |
Completeness | Explicitly answers both 'what' (collections, queryCollection API, MDC rendering, database configuration, etc.) and 'when' ('Use when working with Nuxt Content v3, markdown content, or CMS features in Nuxt'). The 'Use when...' clause is present and clear. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Nuxt Content v3', 'markdown content', 'CMS', 'Nuxt', 'collections', 'queryCollection', 'MDC', 'NuxtStudio', 'i18n'. These cover the primary terms a developer working in this ecosystem would use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: Nuxt Content v3 specifically. The combination of 'Nuxt Content v3', 'queryCollection', 'MDC rendering', and 'NuxtStudio' makes it very unlikely to conflict with other skills, even other Nuxt-related ones. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill that exemplifies good practices: it's concise, provides executable examples, has clear progressive disclosure to reference files, and includes verification steps. The task-based loading checklist is particularly well-designed for token efficiency. Cross-references to related skills (document-writer, nuxt, nuxthub) help with discoverability.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and well-structured. It avoids explaining what Nuxt, markdown, or SQL are. The key concepts table is efficient, and the token budget section at the bottom shows awareness of context window costs. Every section earns its place. | 3 / 3 |
Actionability | Provides fully executable code examples for both content.config.ts and the Vue page component. The quick start is copy-paste ready with a complete collection definition and rendering setup. The verify step ('npx nuxi typecheck') gives concrete validation guidance. | 3 / 3 |
Workflow Clarity | The quick start provides a clear two-step workflow (define collection → create page), includes a verification step with troubleshooting hint ('If queryCollection returns empty, check that content files exist'). The loading checklist provides clear task-based guidance for which references to consult. | 3 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a concise overview, clear one-level-deep references to five specific sub-files, a task-based checklist for loading only relevant files, and an explicit instruction not to load all files at once. Navigation is well-signaled with descriptive labels. | 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- onmax/nuxt-skills
- Commit
00fb59d
- 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.