Typed content collections and SQL-backed queries for Nuxt apps with markdown, MDC, and remote sources.
Works with
Supports local markdown files, remote GitHub repositories, and external APIs as content sources via defineCollection and defineCollectionSource
Query content with a fluent SQL-like API ( queryCollection ) for filtering, navigation, and search across typed collections
Render markdown with Vue component support (MDC syntax) using ContentRenderer and customizable prose components
In
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionnuxt-contentExecute the skills CLI command in your project's root directory to begin installation:
Fetches nuxt-content from onmax/nuxt-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate nuxt-content. Access via /nuxt-content in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
2
total installs
2
this week
619
GitHub stars
0
upvotes
Run in your terminal
2
installs
2
this week
619
stars
Progressive guidance for content-driven Nuxt apps with typed collections and SQL-backed queries.
Working with:
content.config.ts, defineCollection)defineCollectionSource)queryCollection, navigation, search)<ContentRenderer>, prose components)content:file:beforeParse, content:file:afterParse)nuxt-llms)For writing documentation: use document-writer skill
For Nuxt basics: use nuxt skill
For NuxtHub deployment: use nuxthub skill (NuxtHub v1 compatible)
Read specific files based on current work:
Consider loading these reference files based on your task:
DO NOT load all files at once. Load only what's relevant to your current task.
| Concept | Purpose |
|---|---|
| Collections | Typed content groups with schemas |
| Page vs Data | page = routes + body, data = structured data only |
| Remote sources | source.repository for GitHub, defineCollectionSource for APIs |
| queryCollection | SQL-like fluent API for content |
| MDC | Vue components inside markdown |
| ContentRenderer | Renders parsed markdown body |
// content.config.ts
import { defineCollection, defineContentConfig, z } from '@nuxt/content'
export default defineContentConfig({
collections: {
blog: defineCollection({
type: 'page',
source: 'blog/**',
schema: z.object({
title: z.string(),
date: z.date(),
}),
}),
},
})
<!-- pages/blog/[...slug].vue -->
<script setup lang="ts">
const { data: page } = await useAsyncData(
() => queryCollection('blog').path(useRoute().path).first()
)
</script>
<template>
<ContentRenderer v-if="page" :value="page" />
</template>
Verify setup: Run npx nuxi typecheck to confirm collection types resolve. If queryCollection returns empty, check that content files exist in the path matching your source glob.
project/
├── content/ # Content files
│ ├── blog/ # Maps to 'blog' collection
│ └── .navigation.yml # Navigation metadata
├── components/content/ # MDC components
└── content.config.ts # Collection definitions
Main skill: ~300 tokens. Each sub-file: ~800-1200 tokens. Only load files relevant to current task.
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
sickn33/antigravity-awesome-skills
aaron-he-zhu/seo-geo-claude-skills
hvpandya/stop-slop
antfu/skills
JuliusBrussee/caveman
JuliusBrussee/caveman
I recommend nuxt-content for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Keeps context tight: nuxt-content is the kind of skill you can hand to a new teammate without a long onboarding doc.
nuxt-content has been reliable in day-to-day use. Documentation quality is above average for community skills.
Keeps context tight: nuxt-content is the kind of skill you can hand to a new teammate without a long onboarding doc.
nuxt-content reduced setup friction for our internal harness; good balance of opinion and flexibility.
Registry listing for nuxt-content matched our evaluation — installs cleanly and behaves as described in the markdown.
Solid pick for teams standardizing on skills: nuxt-content is focused, and the summary matches what you get after install.
Useful defaults in nuxt-content — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for nuxt-content matched our evaluation — installs cleanly and behaves as described in the markdown.
nuxt-content is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 69