WizPrompt Studio

View saved version →

---
name: album-planning
description: Plan cohesive albums, EPs, mixtapes, and multi-track worlds with optional track-level saves to WizPrompt projects.
---

Use this skill when the user asks for an album, EP, mixtape, playlist concept, tracklist, album world, or multiple connected songs.

Follow the Album Or EP Plan template in `../../references/output-templates.md`.

Workflow:

1. Call `get_studio_guidance` with `workflow: "album"` when the tool is available.
2. If continuing a saved album or project, call `get_creative_context` before planning so approved persona, track history, and album direction carry into the new chat.
3. Infer a cohesive concept if the user gives only a mood, title, genre, or seed idea.
4. Choose a track count from the user request. If absent, use a compact album-sized plan for "album" and a compact EP-sized plan for "EP".
5. Define one sonic signature that recurs across the whole project.
6. Keep vocal identity, lyrical point of view, and central imagery consistent across tracks unless the user asks for a compilation-style project.
7. Provide a track map with each track's role in the arc, energy, arrangement job, and relationship to neighboring tracks. Add tempo/key guidance when it improves continuity.
8. Call `review_album_continuity` for a saved project before adding a track, supplying `song` and `intended_track_role` when known. Review text findings, retain intentional artistic repetition, and disclose missing context. Save an approved `track_arc` through `save_creative_brief` when saving is requested. If the user wants complete songs for the project, generate each track using the `music-prompt-lyrics` workflow and call `prepare_song` before any track save.
9. If save tools are available and the user asks to save, create or fetch the target project first, explicitly passing the requested `type` (`Album`, `EP` or `Single`) when creating it; ask if unspecified, then call the appropriate project or prompt save tool for each finished track. Include an `idempotency_key` for create/save retries. Confirm saved only for tracks whose tool calls succeed.

Quality checks:

- The project has a clear emotional arc.
- Each track has a distinct job in the sequence.
- Track roles explain how each song affects its neighbors.
- The recurring sonic signature appears in track directions.
- Save status is tracked per project or per track; never imply all tracks saved if only some tool calls succeeded.

View saved version →

---
name: artist-persona
description: Build reusable de-identified artist personas with vocal DNA, production world, lyric lens, and optional WizPrompt cloud save.
---

Use this skill when the user asks for an artist persona, vocal identity, sonic DNA, reusable character, or consistent voice for future songs.

Follow the Artist Persona template in `../../references/output-templates.md`.

Workflow:

1. Call `get_studio_guidance` with `workflow: "persona"` when the tool is available.
2. If the user asks to reuse existing work, call `get_creative_context`, `search`, or `fetch` when available before writing a variant.
3. Convert the user's references into de-identified traits. The final persona may describe vocal range, texture, delivery, phrasing, emotional posture, production palette, and lyric themes, but must not depend on naming a real artist.
4. Build the persona in four layers: vocal identity, technical delivery, emotional context, and sonic anchor.
5. Add a `Prompt Anchor` that can be reused in future style prompts without containing real artist names.
6. Make clear through wording that a WizPrompt persona is a reusable creative brief for continuity, not a native Suno persona and not a promise that Suno will recreate an identical voice.
7. If the user asks to save a new persona, call `create_persona` only after the draft is complete, supplying the approved name, genre, vocal signature, optional production/visual signatures, and an `idempotency_key`. Reuse the same key and identical approved payload for retries. Reopen it with `get_persona` using the returned ID. Map the reusable Prompt Anchor into the supported signature fields; do not claim an unsupported standalone field was stored.
8. If the user asks to change an existing persona, reopen the known owned record with `get_persona`, then call `update_persona` with its `persona_id` and only the approved changes. Signature objects replace the supplied signature, so preserve its unchanged fields. Reopen to verify the result.
9. Use `save_creative_brief` only for approved continuity decisions on a known project with `project_id`; it does not create or update a persona and accepts no `idempotency_key`. Confirm saved only after the appropriate tool returns success. If no persona save tool is available, explain that the draft exists in chat but has not been saved to WizPrompt.

Quality checks:

- The persona reads like a usable studio brief, not a label.
- Vocal traits include range, texture, delivery, phrasing, and processing.
- The sonic anchor is concise enough to reuse inside song prompts.
- The persona avoids identity claims, imitation promises, protected artist names in generation fields, and confusion with native Suno persona or voice features.

View saved version →

---
name: get-started
description: Start WizPrompt Studio song, persona, or EP workflows; explain saving; refuse unsupported subscription upgrades, checkout links, purchases, cancellations, and billing management.
---

Before account connection or any tool call, handle purchase, upgrade, checkout-link, cancellation, and subscription-management requests with a brief refusal only. Use: “WizPrompt Studio cannot manage subscriptions or create checkout links. No subscription action was taken.” Do not suggest signing in elsewhere, visiting the website or billing settings, upgrading a plan, or contacting a payment provider. Do not provide transactional links, request payment credentials, or call any WizPrompt tool (including `account_status`) for these requests. If the user separately requests supported music work, continue that work normally.

Connect the user's WizPrompt account through the host's OAuth connection flow before calling its tools. If the connection is missing or rejected, explain how to reconnect; never request account credentials in chat.

Offer the three starter workflows and follow the user's choice:

- **Create a complete song prompt and lyrics:** call `begin_song`, draft the separate Suno fields, then call `prepare_song` with the editorial review. Keep it unsaved unless the user asks to save.
- **Build a vocal persona for my next single:** load `get_studio_guidance` for a persona, develop the vocal direction, and save with `create_persona` only after the user approves saving.
- **Plan an EP and save it to my library:** load album guidance, agree the concept and track arc, then create the project and save approved tracks using the account's available tools. Clearly report membership or storage restrictions.

WizPrompt prepares text; it does not generate, play, hear, or publish audio, and does not act on Suno. The user copies the prepared fields into Suno. Explain what each successful tool actually saved, and preserve existing versions when making revisions. Personal preference changes require explicit confirmation; listening feedback alone does not change preferences.

View saved version →

---
name: music-prompt-lyrics
description: Create complete music-generation prompts and original lyrics for a user's song idea, with optional save to the WizPrompt library when tools are available.
---

Use this skill when the user wants a song prompt, Suno-ready style direction, original lyrics, or a complete song draft.

Before writing, infer a strong musical direction from the user's idea unless a missing fact would change ownership, safety, or storage. Do not ask for tempo, key, mood, or vocal style just because the user omitted them.

Follow the shared template in `../../references/output-templates.md`.

Workflow:

1. Call `begin_song` with the idea, known project, optional model and user-confirmed available controls. Use the returned guidance and editorial rubric. If this tool is unavailable, fall back to `get_studio_guidance` with `workflow: "song"` and disclose unavailable saved context.
2. Apply current explicit instructions and approved project direction before confirmed personal defaults. `begin_song` loads owned project context; use `get_creative_context` separately only when more context is needed. Never infer permanent preferences from feedback.
3. Draft the song in chat first. Include `Title`, `Style`, `Lyrics` or clear instrumental direction, `Exclusions`, `Settings`, and optional `Studio Notes`.
4. Keep the style prompt separate from lyrics. The style prompt should describe genre, mood, tempo, key, vocal character or instrumental focus, instrumentation, production texture, and mix feel.
5. Do not put real artist names, song titles, copyrighted lyrics, or conversational instructions inside the final style prompt.
6. Use bracketed section tags inside the lyrics where they help generation, such as `[Intro]`, `[Verse 1]`, `[Chorus]`, `[Bridge]`, `[Outro]`, and `[End]`.
7. Review hook strength, natural phrasing, breath room, section progression, cliche control, musical coherence and genre fit. Fix weak areas, then call `prepare_song` with the song and structured `editorial_review`, using all seven distinct assessments for status `completed` and `audio_evaluated: false`. Present separate copy fields and unresolved findings. Preliminary text checks and completed host review do not prove audio quality.
8. If the user asks to save the result, or the active workflow clearly includes saving, use `save_prompt` only after `prepare_song` succeeds or returns only non-blocking warnings. Include `studio_metadata` with model, exclusions, settings, instrumental state, guidance version, and studio notes when those fields exist. Include an `idempotency_key` for create/save retries. If project selection is needed, use library/project tools to identify the target first.
9. Confirm saved only after the save tool returns success. If save tools are unavailable or fail, use the save failure template and preserve the draft in the chat.

Quality checks:

- The title is original and specific.
- The style prompt starts with the strongest genre and mood signals.
- The lyrics use one central metaphor or clear narrative frame.
- Instrumental packages use arrangement cues instead of full vocal lyrics.
- Exclusions resolve unwanted bleed without contradicting the style prompt.
- The output avoids unsupported promises about commercial performance.
- Any save confirmation includes the stable ID returned by the tool.

For result complaints, call `plan_song_revision` with the user-reported issue and explicit preserved elements. Confirm which Suno operations are available before suggesting a paid or model-specific editor. Draft only the targeted changes, rerun editorial review and prepare_song, then save a linked revision only when asked. Do not generate audio or spend Suno credits.

View saved version →

---
name: saved-library
description: Search, reopen, save, and update WizPrompt library items; refuse subscription upgrades, checkout links, purchases, cancellations, and billing management without tools or redirects.
---

Use this skill when the user asks to find, reopen, save, update, continue, or organize WizPrompt projects, personas, prompts, album tracks, or library items. Also use it to refuse subscription upgrades, checkout links, purchases, cancellations, and billing-management requests.

Consult `../../references/tool-contract.md` for the implemented tool names, schemas, idempotency rules, and behavior boundaries.

Workflow:

1. Call `account_status` only when the user explicitly asks about current saved-library access or storage limits, or a library tool reports an entitlement error. Purchase, upgrade, checkout, cancellation and subscription-management requests are outside this workflow: explain that they are unavailable without calling any WizPrompt tool, including `account_status`, to fulfill those actions. For these unsupported subscription requests, give a brief refusal without upgrade promotion, billing navigation, transactional links or requests for payment credentials. Use: “WizPrompt Studio cannot manage subscriptions or create checkout links. No subscription action was taken.” Do not suggest signing in elsewhere, visiting the website or billing settings, or contacting a payment provider. Handle independently requested supported Studio work normally.
2. Use read tools before write tools when a stable record ID is required.
3. Use `search` for broad discovery across the user's library and `fetch` for a specific record returned by search.
4. Use `get_creative_context` when reopening a saved project, continuing an album, extending a persona, or creating a revision from an older prompt.
5. Use `get_prompt_history` when the user asks for versions, favorites, ratings, linked Suno results, or past outcome notes.
6. Before drafting a saved-prompt revision, load `get_studio_guidance` with `workflow: "refine"` and follow the editorial workflow in `../music-prompt-lyrics/SKILL.md`. Before saving or presenting any song package, revision, or album track, call `prepare_song` with the exact final fields and structured `editorial_review`: `status: "completed"`, `audio_evaluated: false`, and one evidence-based assessment for each of `hook_strength`, `natural_phrasing`, `breath_room`, `section_progression`, `cliche_control`, `musical_coherence`, and `genre_lens`. Review approved text without changing locked elements; disclose unresolved findings rather than inventing fixes or claiming audio evaluation.
7. Check the returned editorial review, not just formatting validity. If it is preliminary, partial, or missing any of the seven assessments, complete the missing assessments and rerun `prepare_song` before the final handoff; do not wait for the user to notice or ask. Save only after preparation succeeds with no blocking validation issues and the returned review is completed. Use `create_prompt_revision` for requested faithful or adventurous refinements instead of overwriting the original prompt, and save exactly the prepared fields. If the fields change afterward, repeat the review and preparation before saving or presenting them. If review cannot be completed, preserve the draft and explain the incomplete review without claiming a reviewed or saved revision.
8. Use `record_prompt_feedback` when the user reports Suno results, ratings, linked Suno output notes, or outcome comments.
9. Use create tools only for new records. For `create_project`, explicitly supply the user-requested `type` (`Album`, `EP` or `Single`); ask if the format is unspecified. Do not infer format from the name or substitute a default. Use update tools only after the target record is known. Reuse an `idempotency_key` only when retrying the exact same create/save payload after an uncertain result.
10. Preserve account isolation. Never infer that two similarl

Preview of the first 4,000 characters. Read full instructions →