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 trigger terms are natural and comprehensive, covering both the framework name and specific API/feature terms developers would reference. The description is concise yet thorough, making it easy for Claude to select this skill appropriately.
| 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 features', 'Nuxt', 'collections', 'queryCollection', 'MDC', 'NuxtStudio', 'i18n'. These cover the primary terms a developer working with this framework 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 generic markdown, CMS, or other Nuxt skills. | 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 progressive disclosure and token efficiency. The main file serves as a concise hub with executable quick-start code, a clear key concepts table, and well-organized references to deeper content. The cross-references to related skills (document-writer, nuxt, nuxthub) and the task-based loading checklist are particularly effective patterns.
| 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 workflow is clear: define collections in content.config.ts → create content files → query and render. The verify step with typecheck and the troubleshooting hint about empty queryCollection results provide validation checkpoints. The loading checklist guides task-based file selection clearly. | 3 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a concise overview pointing to five clearly-labeled reference files, each with a one-line description of when to load it. The checklist format with explicit 'DO NOT load all files at once' instruction is ideal. References are one level deep and well-signaled. | 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
48efc7a
- 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.