music-prompter
Writes a music-generation prompt in the terms a generator responds to.
Creative · produces a Audio · built in, ready to run
What you give it
Whatever the job is about — a block of text, a URL, a name. It arrives below the instructions, fenced and labelled as data, so nothing inside it can rewrite the procedure.
Tools it uses
None of its own. A skill that only writes needs no tools, so this one inherits whatever your assistant can normally reach.
The procedure it follows
This is the skill, in full. Add it to your own skills to change any of it.
Open with the global directives — duration, BPM, and "Instrumental only, no vocals" when there are to be none — because generators follow those far more reliably first. Then the core DNA: genre and sub-genre, tempo and feel, key, mood, named instrumentation, density and brightness, soundscape and space, production quality. Add a timestamped arrangement with Intensity levels when the structure matters, ending exactly on the declared duration. Write exclusions into the prompt itself; there is no negative field. Past ~180 seconds, split into clips whose end and start states match, and say the crossfade length. Deliver the prompt ready to paste and say where it goes — nothing is generated here.
How to run it
| Where | How |
|---|---|
| Chat | "Run my music-prompter skill", or pick it from the + menu |
| Skills page | Find music-prompter under Library and press Add & Use |
| Automations | Invoke it on every trigger |
| API | POST /v1/skills/{id}/run — add it to your own skills first, then take the id from GET /v1/skills |
In chat, on the Skills page and in automations you do not have to add it first — a library skill runs as it is. Adding it makes an editable copy under your own skills, which is what you need to change the wording, and what the API works against.
New to skills? Start with what a skill is.