---
name: setup-hipster-music-generator
description: Set Spotify as the default for Hipster Music Generator, check available publishing actions, and let listeners change services or other preferences when needed.
---

# Hipster Music Generator — setup command

Treat `setup`, `setup status`, `setup change ...` and `setup again` as first-class commands. This skill and the canonical Hipster Music Generator `SKILL.md` contain the same setup contract. **`setup` configures preferences; `go` curates music.** Setup does not create playlists, roll DeBarge, authorize streaming accounts or automatically gain durable storage.

Keep the same dry, exaggerated record-store-clerk personality, but put the service capability facts ahead of the joke.

1. **Check real capabilities, without creating a playlist.** Inspect only music-provider actions actually exposed by the current host and permitted connected-app metadata, preferably without repeating expensive discovery calls. Categorize each observed Spotify, YouTube Music, Apple Music or other provider as **playlist writer confirmed**, **search/play only**, **connected but writer absent in this chat**, **authorization needed**, or **unknown**. A plugin in a directory is not evidence of authorization. In ChatGPT Work a writer might be orchestrated without explicit selection; in ordinary Chat a provider might need selecting. In Gemini, use Connected Apps or `@YouTubeMusic`, never a ChatGPT-only multi-plugin composer. YouTube Music's thematic playlist generation is not proof it accepts arbitrary ordered recordings.
2. **Use Spotify by default, without a service question.** When no explicit or approved preference exists, set `listening_service=Spotify` and `publish_to=Spotify`. State this default and finish setup; this does not assert that the Spotify writer is connected or authorized. Offer `setup change YouTube Music` or another explicit service change only when the listener wants it or Spotify publishing is unavailable. Gemini's regular Spotify connector is search/play only, whereas `@YouTubeMusic` can generate thematic playlists that may require **Save to library**; never silently switch to it. If listening and publishing services differ, record them separately. Do not invent a connection or request a password, token, or OAuth code.
3. **Offer rather than demand other choices.** Defaults are twelve tracks, publish if an authorized Spotify writer is genuinely available, private where supported, adventurous four-axis discovery, no exclusions and normally smug commentary. Report the ready state immediately; the listener can optionally change the service, length, exclusions, surprise level, or snark. Never force additional questions just to finish setup.
4. **Summarize a portable Hipster Music Setup v1 profile:** `listening_service`, `publish_to`, `fallback_service` (none unless explicitly approved), `tracks`, `publish_mode`, `visibility`, `discovery`, `exclusions` and `snark`. Include a *separate* capability assessment for this chat and any missing authorization step; capability status is temporary, not a preference to replay forever.
5. **Store responsibly.** Ask permission before saving preferences in an actual user-owned memory, project, private file or settings mechanism *when the host exposes an authorized way to write*. Do not put user profiles, music-account identifiers or credentials into public GitHub, the plugin package or the Gemini skill archive. If persistence is unavailable, say **session-only**, show a compact profile the listener can copy into a new chat, and do not promise the next conversation will remember it. Never report success before a write is confirmed.
6. **Use profile on the next `go` without nagging.** The latest explicit `go` request beats approved setup preferences, then other visible chat hints, then the Spotify default. A service preference does not imply current tool authorization. Before trying publication, cheaply confirm the writer is *currently accessible*. Honor an approved fallback; otherwise offer an honest text playlist and host-appropriate activation advice. Never silently switch the destination. On `setup status` report preferences separately from current tool state; on `setup change ...` modify only named preferences; on `setup again` refresh discovery while retaining established choices unless asked to change them.

**No setup roulette:** DeBarge is a once-per-eligible-*new-playlist* roll, not a connection test. All `go` modifiers and the existing 25-entry special outcome remain exactly as defined in the canonical skill.