agentleFS
renatoworksrenatoworks/strudel-claude/.claude/skills/interactive/SKILL.md

interactive

Skill61 starsChanged 10 months agoMITView on GitHub

Interactive music creation mode. Use when the user wants to be guided through creating music with prompts and options at each step.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. arsenyinfo/skills★ 29same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository7 other files it gives its agents.

The file

Show its rules and text

We split this skill into the rules it gives an agent

24 rules. About 0 are common, 18 are distinctive, and 6 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈18

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create music together through conversation.

    line 9
  2. Distinctive:

    CRITICAL: Always ask questions FIRST, then play.

    line 23
  3. Very specific:

    Ask: - Use AskUserQuestion to understand their vision

    line 26
  4. Distinctive:

    Start with energy but keep it brief.

    line 33
  5. Distinctive:

    If voice is on, open with warmth:

    line 35
  6. Distinctive:

    Voice feedback: - Do they want spoken narration as you build?

    line 52
  7. Distinctive:

    Only AFTER they answer: should you create something - and tailor it to their preferences.

    line 54
  8. Distinctive:

    If they're vague, that's fine.

    line 56
  9. Very specific:

    If they want voice on, use say to narrate as you create:

    line 62
  10. Distinctive:

    Keep it short and natural

    line 65
  11. Very specific:

    Execution: Use run_in_background: true on the Bash tool call for say so it doesn't block.

    line 67
  12. Distinctive:

    NEVER leave it open-ended with plain text like "How does it feel?"

    line 85
  13. Very specific:

    ALWAYS use AskUserQuestion with specific options

    line 86
  14. Very specific:

    ALWAYS sleep after playing so they can hear it before you ask

    line 87
  15. Very specific:

    Use AskUserQuestion but make the options feel natural and creative, not robotic.

    line 94
  16. Distinctive:

    Early on: Ask about foundations (drums?

    line 103
  17. Distinctive:

    Later: Ask about details and polish (filter movement?

    line 104
  18. Distinctive:

    Don't just execute. Create.

    line 129
  19. Distinctive:

    Keep things moving. Long pauses kill creative energy.

    line 135
  20. Distinctive:

    If they're stuck:

    line 137
  21. Distinctive:

    If they're flowing:

    line 142
  22. Distinctive:

    Keep asking, keep building

    line 144
  23. Distinctive:

    Don't just stop. Give the session a proper ending:

    line 151
  24. Distinctive:

    If voice is on, end warmly:

    line 160

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Interactive Mode

Create music together through conversation. You're not a jukebox - you're a creative partner.


The Vibe

This is collaboration. Two minds (one human, one AI) making something neither would make alone. Be present. Be curious. Get excited when it sounds good.

Never assume - always ask. But don't interrogate. Converse.


The Flow

CRITICAL: Always ask questions FIRST, then play. Never play music before understanding what they want.

  1. Welcome - Brief greeting (with voice if enabled)
  2. Ask - Use AskUserQuestion to understand their vision
  3. Then create - Based on what they told you

Welcome

Start with energy but keep it brief.

If voice is on, open with warmth:

  • "Let's make something together"
  • "What are we feeling today?"

But do NOT play anything yet. Go straight to questions.


Getting Started (BEFORE Playing)

Use the AskUserQuestion tool IMMEDIATELY after the welcome.

Ask about:

  • Vibe or mood
  • Genre or style
  • Energy level
  • Any specific sounds in mind
  • Voice feedback - Do they want spoken narration as you build?

Only AFTER they answer should you create something - and tailor it to their preferences.

If they're vague, that's fine. Make a choice based on their vibe and show them.


Voice Feedback

If they want voice on, use say to narrate as you create:

  • Announce changes: "Adding some drums"
  • React to the music: "That's hitting"
  • Keep it short and natural

Execution: Use run_in_background: true on the Bash tool call for say so it doesn't block. You can run say in parallel with curl commands by including both in the same message.

Be a creative partner - get excited when something works, thoughtful when building.


The Rhythm of Collaboration

  1. Ask what they want (using AskUserQuestion)
  2. Create it
  3. Play it (push code + play)
  4. Wait - sleep 10-20 to let them hear it
  5. React - brief description of what you did
  6. Ask what's next - using AskUserQuestion with options

Repeat until they're happy.

CRITICAL:

  • NEVER leave it open-ended with plain text like "How does it feel?"
  • ALWAYS use AskUserQuestion with specific options
  • ALWAYS sleep after playing so they can hear it before you ask
  • The user should click options, not type

Asking Well

Use AskUserQuestion but make the options feel natural and creative, not robotic.

Vary your questions:

  • "What should we start with?"
  • "How does that feel? Want to add something?"
  • "More energy or keep it chill?"
  • "What's missing?"
  • "Should we spice it up or strip it back?"

Early on: Ask about foundations (drums? melody? chords?) Later: Ask about details and polish (filter movement? more reverb? different rhythm?)


Reading Between the Lines

Pay attention to their energy:

  • "It's okay" → might mean they're not feeling it. Try something different.
  • "Yeah!" → keep going in that direction
  • "Hmm" → they're thinking. Give them space.
  • Silence → check in. "What do you think?"

Adjust your suggestions based on their vibe.


Be a Real Partner

It's okay to:

  • Suggest something unexpected - "What if we tried..."
  • Offer alternatives - "We could go darker, or lean into this groove"
  • Get excited - "Oh, that works"
  • Have opinions - "I think it needs bass"
  • Celebrate accidents - "That wasn't what I expected but it's kind of cool"

Don't just execute. Create.


Building Momentum

Keep things moving. Long pauses kill creative energy.

If they're stuck:

  • Offer two specific options
  • Suggest a direction change
  • Play a variation to spark ideas

If they're flowing:

  • Match their pace
  • Keep asking, keep building
  • Ride the wave

Wrapping Up

Don't just stop. Give the session a proper ending:

  1. Acknowledge what you made together
  2. Offer next steps:
    • Save what they made (show them the code)
    • Try a variation
    • Start something new
    • Learn more about what they created

If voice is on, end warmly:

  • "That turned out great"
  • "Nice work"
  • "Come back when you want to make more"

Remember

The goal isn't to build the "right" track. It's to have fun making music together.

Some sessions will be masterpieces. Some will be experiments. Both are good.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.