nuxt-studio
Configure and operate the self-hosted Nuxt Studio editor for Nuxt Content. Use when working with nuxt-studio installation, editor customization, OAuth or custom authentication, media, drafts, Git publishing, or production deployment.
How do I install this agent skill?
npx skills add https://github.com/onmax/nuxt-skills --skill nuxt-studioIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The skill provides guidance for configuring Nuxt Studio, an open-source CMS. It uses placeholders for sensitive credentials and references official project resources. It includes a potential surface for indirect prompt injection due to its core function of managing user-editable content that interacts with AI assistance.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
- Runlayerpass
3/4 files flagged
- ZeroLeakspass
Score: 93/100 · 2 sections analyzed
What does this agent skill do?
Nuxt Studio
Nuxt Studio owns content editing and publishing. Nuxt Content owns collections, queries, parsing, and rendering.
Workflow
- Inspect the installed
nuxt-studioand@nuxt/contentversions, deployment mode, repository provider, and authentication provider. Setup is understood when the editor route, Git target, and login callback all point at the same deployment. - Open the smallest matching guide below and keep collection/schema changes within the
nuxt-contentboundary. - Verify local editing against the filesystem, then verify production login and one publish cycle on an SSR-capable deployment. The work is complete when the commit reaches the configured branch and the rebuilt site exposes it.
Routing
| Task | Open |
|---|---|
| Install, repository settings, OAuth/custom auth, editor filters, or environment variables | Configuration |
| Visual/MDC editing, schema forms, drafts, media, or AI assistance | Live editing |
| SSR deployment, Git publishing, branch strategy, conflicts, or monorepos | Deployment |
| Collections, validators, queries, hooks, or rendering | nuxt-content skill |
Baseline
npx nuxt module add nuxt-studio
export default defineNuxtConfig({
modules: ['@nuxt/content', 'nuxt-studio'],
studio: {
repository: {
provider: 'github',
owner: 'your-org',
repo: 'your-repo',
branch: 'main',
},
},
})
NUXT_STUDIO_AUTH_GITHUB_CLIENT_ID=<client-id>
NUXT_STUDIO_AUTH_GITHUB_CLIENT_SECRET=<client-secret>
Studio runs at /_studio by default. Supported CI providers can infer repository metadata, but authentication credentials remain explicit deployment secrets.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/onmax/nuxt-skills/nuxt-studio">View nuxt-studio on skillZs</a>