{"id":70919,"plugin_id":"plugin_asdk_app_6ac6e9f5b964819189aed37b910099dc","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-29T19:01:07.921Z","digest":"aebc67b66b60a8ad7433cfdf90b2dd611a2b83324a294c69364822568e84a07e","against":null,"payload":{"description":"Make a new beat or song in CookUp from an idea, genre, mood, reference or tempo, for example \"make a dark trap beat at 140\" or \"a mellow lo-fi loop with warm keys\". Use for new music, not for changing an existing session (edit-a-session) or for sampling a song (flip-a-sample).","included_files":[],"name":"make-a-beat","skill_md_contents":"---\nname: make-a-beat\ndescription: Make a new beat or song in CookUp from an idea, genre, mood, reference or tempo, for example \"make a dark trap beat at 140\" or \"a mellow lo-fi loop with warm keys\". Use for new music, not for changing an existing session (edit-a-session) or for sampling a song (flip-a-sample).\n---\n\n# Make a beat\n\nExplicit user instructions always take priority over these guidelines.\n\n## Input\n- The idea: genre, mood, tempo, key, instruments, length, references.\n- If the user gives only a vague request (\"make a beat\"), make reasonable choices and say what you chose. Ask only when a required fact is missing and guessing would waste the result, such as a session the user asked you to add to but did not name.\n\n## Steps\n1. **Quick build** (the user wants something fast, or gives a short prompt): call `create_beat` with the prompt and a full `plan`:\n   - bpm, tonic and mode;\n   - chord degrees for 8 bars, with bars 5–8 developing bars 1–4;\n   - one memorable melody motif with rests;\n   - bass on chord roots that answers the kick;\n   - a one-bar drum pocket that fits the genre.\n\n   Use `plan.bars` for the requested length (default 32).\n2. **Produced build** (a substantial or detailed request):\n   1. Call `prepare_production`.\n   2. Write a few short private ideas and compare them with `review_production_draft`. Send the full cumulative commands each time.\n   3. Develop the strongest idea.\n   4. Save the final batch once with `apply_session_edit`.\n3. Choose sounds as in the choose-sounds skill: the user's own kits first, and audition the kick, snare or clap, 808 or bass, and lead before committing them.\n4. If the host can receive audio, render with `render_audio_preview`, then listen with `listen_audio_preview` before describing how it sounds.\n5. End with one `open_session` call so the user can press Play.\n\n## Output\n- Session name and code.\n- Tempo and key.\n- The parts you made.\n- Anything CookUp substituted or could not do.\n\n## Never\n- Invent sound IDs, session codes or edit results.\n- Say the beat sounds good, mixed or finished unless you listened to returned audio. Say it is ready to audition instead.\n- Claim the beat was saved before `create_beat` or `apply_session_edit` confirms it.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}