Skip to content
Back to skills

Nuxt Studio

ASecurity

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.

  • 714 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 5, 2026
securitybashgit

Works with

  • cli

Security analysis

A100/100

Pro scans all 4 files and shows the line behind each finding

Scanned September 5, 2026

npx -y skills add onmax/nuxt-skills --skill nuxt-studio --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Nuxt Studio?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Nuxt Studio
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/onmax-nuxt-studio/badge)](https://www.skillsdirectory.com/skills/onmax-nuxt-studio)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: nuxt-studio
description: 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.
license: MIT
---

# Nuxt Studio

Nuxt Studio owns content editing and publishing. Nuxt Content owns collections, queries, parsing, and rendering.

## Workflow

1. Inspect the installed `nuxt-studio` and `@nuxt/content` versions, 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.
2. Open the smallest matching guide below and keep collection/schema changes within the `nuxt-content` boundary.
3. 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](references/configuration.md) |
| Visual/MDC editing, schema forms, drafts, media, or AI assistance                         | [Live editing](references/live-editing.md)   |
| SSR deployment, Git publishing, branch strategy, conflicts, or monorepos                  | [Deployment](references/deployment.md)       |
| Collections, validators, queries, hooks, or rendering                                     | `nuxt-content` skill                         |

## Baseline

```bash
npx nuxt module add nuxt-studio
```

```ts
export default defineNuxtConfig({
  modules: ['@nuxt/content', 'nuxt-studio'],
  studio: {
    repository: {
      provider: 'github',
      owner: 'your-org',
      repo: 'your-repo',
      branch: 'main',
    },
  },
})
```

```bash
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.

Files in this skill

  • SKILL.md2.4 KB
  • references/configuration.md3.3 KB
  • references/deployment.md2.9 KB
  • references/live-editing.md3.1 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.