clawtunes

**Quick judgment** `clawtunes` is a capable, macOS-specific skill for controlling Apple Music from an automated or terminal-based environment. It is feature-rich for playback and playlist management but constrained by its platform (macOS only, requires Apple Music and AppleScript automation permissions). Suitable for users who intentionally want scripted or chat-driven control of Apple Music on a Mac; not applicable outside that context. **What it does well** - Controls core playback: play/pause, next/previous, volume (absolute and relative), mute/unmute, shuffle, and repeat. - Plays specific songs, albums, or playlists by name, and exposes search options to limit or filter results. - Manages playlists (list, create, add/remove tracks), and can love/dislike the current track. - Handles AirPlay selection, allowing remote/device-targeted playback from the Mac. - Supports Apple Music catalog search for discovery (though adding catalog items to the library still requires the Apple Music app). **Notable constraints and reliability considerations** - **Platform limitation:** macOS-only and tightly coupled to the Apple Music app via AppleScript; it will not function on other OSes or where Apple Music is not present/configured. - **Automation permissions:** Requires the user to grant automation permissions (System Settings → Privacy & Security → Automation). If missing, commands may fail until the user approves. - **Interactivity pitfalls:** The CLI is designed to be used with `--non-interactive` (`-N`) to avoid prompts. If a wrapper skill does not consistently enforce this, commands may hang waiting for user input, especially when multiple search matches exist. - **Matching ambiguity:** Common song/album/playlist names can yield multiple matches, requiring more specific queries or the `--first` (`-1`) flag, which may reduce determinism in automated flows. **Risk profile** - **Data & privacy:** Operates within the Apple Music domain: library metadata, playlists, and AirPlay device selection. It does not obviously expose broader filesystem or sensitive system operations. However, it can reveal what is playing, existing playlists, and AirPlay device names (which may encode locations or people’s names). - **Stateful changes:** Can modify user data in Apple Music (playlist contents, love/dislike status, playback position, volume, AirPlay targets). These are reversible but may be surprising if the user does not expect automation to alter playlists or redirect audio. - **Device impact:** Volume and AirPlay changes affect the audible environment and possibly shared speakers. Misuse could cause disruptive playback (e.g., loud audio on shared devices), but damage risk is low. **Recommended scenarios** - Users running a **macOS-based assistant** or automation agent who explicitly want the agent to control Apple Music (e.g., “play my focus playlist at low volume,” “skip this track,” “add this song to Road Trip”). - **Developers or power users** automating music playback, volume control, or playlist management from scripts, cron jobs, or chat-based workflows. - **Home or office setups** where a Mac acts as a media host and AirPlay hub, and the assistant needs to move playback across speakers or toggle playback hands-free. **Less suitable for** - Any environment that is not macOS with Apple Music installed and configured. - Users who do not want automated changes to their playlists, track ratings, or AirPlay routing. - Scenarios requiring deterministic behavior with ambiguous media titles, unless the skill/wrapper robustly handles specificity and `--non-interactive`/`--first` flags.