Mozonic

View saved version →

---
name: mozonic-fix-my-mix
description: Use when the user asks what's wrong with a mix, wants it improved, or says "fix it" — interpreting Mozonic's analysis, running the DSP autofix (optionally with a genre flavor or a mastering pass), and delivering the corrected file.
---

# Analyze and fix a mix with Mozonic

## 1. Locate the mix

Find it with `mozonic_list_mixes` (or use a mix ID from an earlier response).
If the song is not in the library yet, direct the user to upload it in the
Mozonic app at https://app.mozonic.com first.

## 2. Read the analysis

`mozonic_get_mix(mix_id=...)` returns the analysis. Translate it for
a musician — talk about muddy low end, harsh highs, squashed dynamics, or
quiet loudness rather than raw numbers, and quote the numbers (LUFS, dB
ranges) as supporting evidence. Lead with the 2–3 findings that matter most.

## 3. Run the autofix

`mozonic_correct_mix(mix_id=...)`. Options:

- `genre` plus `genre_intensity` — for example, `genre="hiphop"` and
  `genre_intensity=0.5` to flavor the correction.
  Genres: pop, hiphop, rock, edm, rnb, acoustic, jazz, lofi, ambient,
  country (or none). Only add this when the user names a genre or vibe.
- `target_profile` — appends a mastering pass after correction
  (streaming_default, loud_streaming, club_loud, podcast, commercial_loud).
  Use when the user wants a release-ready file, not just a fixed mix.

The original audio is never overwritten — corrections create a new render, so
it is always safe to run.

## 4. Wait, then deliver

Correction is asynchronous: poll `mozonic_jobs_active` every 15–30 seconds and
only report completion when the job finishes. Then get the file:
`mozonic_download_mix(mix_id=..., download_type="corrected")` — or
`download_type="mastered"` if you passed a `target_profile` in step 3. Present
the presigned URL and mention it expires, so download promptly.

## 5. Close the loop

Offer the natural next steps: compare against the original
(`download_type="original"`), discuss the changes via `mozonic_chat`
(pass `mix_id` for context), or master it for release (see the
mozonic-master-a-track skill).

View saved version →

---
name: mozonic-get-started
description: Set up Mozonic after installation, confirm the account connection, and choose the first supported library workflow.
---

# Get started with Mozonic

1. Connect a Mozonic Pro account when prompted, then call `mozonic_auth_me` to
   confirm the account and plan.
2. This plugin works with audio already in the Mozonic library. For a local
   file, direct the user to upload it in https://app.mozonic.com first.
3. List the library with `mozonic_list_mixes`, then inspect a mix with
   `mozonic_get_mix` or queue correction with `mozonic_correct_mix`.
4. Long-running work is asynchronous. Use `mozonic_jobs_active` to check
   progress; only offer a download after the render completes.

View saved version →

---
name: mozonic-master-a-track
description: Use when the user wants a track mastered — "master this", "make it release-ready", "loud enough for Spotify/club" — covering target-profile choice and both mastering paths (standalone mastering mode, or mastering a mix already in the library).
---

# Master a track with Mozonic

## 1. Choose the target profile from what the user says

- Spotify / Apple Music / "streaming", or no stated target →
  `streaming_default` (the safe default)
- "as loud as possible on streaming" → `loud_streaming`
- DJ set / club / festival playback → `club_loud`
- spoken word / podcast → `podcast`
- ads / sync / broadcast → `commercial_loud`
- user gives custom specs → `custom` (standalone mastering mode only)

Say which profile you chose and why; ask only if genuinely ambiguous.

## 2. Pick the path

**A. The song is already in the Mozonic library as a mix** — master it via
correction: `mozonic_correct_mix(mix_id=..., target_profile=...)`,
then download with `download_type="mastered"`. (`custom` is not available on
this path.)

**B. A standalone mastering session already in Mozonic** — list sessions with
`mozonic_list_mastering_sessions`, render with
`mozonic_render_mastering_session(session_id=...)`, then download with
`mozonic_download_mastered_track(session_id=..., variant="mastered")`. Use
`variant="input"` to fetch the original for A/B comparison.

**C. A local file not yet in Mozonic** — the plugin cannot upload audio bytes.
Ask the user to upload it in https://app.mozonic.com, then continue using path
A or B once it appears in their library.

## 3. Deliver like a mastering engineer

Mastering is asynchronous — poll, don't claim early completion. When done,
present the download link (it expires), state the profile used, and offer an
A/B against the input. If the user dislikes the result, suggest a different
profile (e.g. streaming_default → loud_streaming) and re-run; each master is
a new render and nothing is overwritten.

View saved version →

---
name: mozonic-upload-a-song
description: Use whenever the user wants to get a local song, mix, track, or audio file into Mozonic from ChatGPT or Codex.
---

# Upload a song to Mozonic

This directory plugin intentionally cannot upload audio bytes or generate S3
presigned URLs. Do not ask for a file path, base64 payload, or file metadata.

Tell the user to upload the audio in the Mozonic app at
https://app.mozonic.com. Once it appears in their library, use
`mozonic_list_mixes` to find it and continue with analysis, correction, or
mastering. For a standalone mastering upload, the same rule applies: upload in
the Mozonic app, then use `mozonic_list_mastering_sessions`.

Requires a Mozonic Pro account.

View saved version →

---
name: mozonic-work-with-stems
description: Use when the user has multiple stem files (drums, bass, vocals, …) or a folder/ZIP of stems and wants Mozonic to analyze them or render a mixed (optionally mastered) bounce.
---

# Work with stems in Mozonic

## 1. Find an existing stem session

The directory plugin works with stem sessions already created in the Mozonic
app. For local stem files or a ZIP, direct the user to upload and create the
session at https://app.mozonic.com first. Then find it with
`mozonic_list_stem_sessions` and inspect it with
`mozonic_get_stem_session(session_id=...)`.

## 2. Render

When analysis is done:
`mozonic_render_stem_session(session_id=..., output_mode=...)`

- `output_mode="mix"` — balanced stereo bounce
- `output_mode="mastered_mix"` — bounce + mastering; add `target_profile`
  (streaming_default, loud_streaming, club_loud, podcast, commercial_loud)

Also async — poll, then fetch artifacts with
`mozonic_download_stem_session(session_id=...)`.