From ableton-save
Automates saving Ableton Live projects on macOS using AppleScript and Python. Navigates Save As dialog, handles paths, and enters filenames on save requests.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ableton-save:ableton-saveThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill provides automated saving functionality for Ableton Live projects on macOS using AppleScript and Python integration. When users need to save their current Ableton Live project to a specific location, this skill handles the automation by navigating to the target directory and entering the filename.
This skill provides automated saving functionality for Ableton Live projects on macOS using AppleScript and Python integration. When users need to save their current Ableton Live project to a specific location, this skill handles the automation by navigating to the target directory and entering the filename.
Enable users to save Ableton Live projects through natural language commands or explicit slash commands. The skill uses AppleScript automation to interact with Ableton Live's Save As dialog, navigating to directories and entering filenames automatically.
Trigger this skill when users:
When a user asks to save an Ableton project with a path like:
"Save the ableton project to ~/Music/Projects/song.als" "Save my live set to ../backups/test.als"
Execute the save command with the specified path:
/ableton-save:save-live-set <path>.als extension is optionalThe save functionality is implemented through:
Python wrapper (scripts/ableton_save.py)
AppleScript (scripts/save_ableton_project.scpt)
| User Query | Action |
|---|---|
| "Save to /path/to/file.als" | Execute /ableton-save:save-live-set /path/to/file.als |
| "Save the project" | Ask for destination path |
| "Backup to foo.als" | Execute /ableton-save:save-live-set foo.als |
npx claudepluginhub mattypie/alsdiff --plugin ableton-saveCreates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.