Mopidy

Control a Mopidy music system via Mopidy JSON-RPC for everyday listening, queue management, and playback control. Use when the user wants to search for music...

Security Scan

The skill's code, required binaries, and environment variable match its stated purpose (controlling a Mopidy JSON-RPC endpoint) and do not request unrelated credentials or perform unexpected actions.

Purpose & Capability

Name/description (Mopidy JSON-RPC control) align with required binaries (curl, jq, python3), the required env var (MOPIDY_URL), and the provided scripts which call Mopidy methods. Everything requested is reasonable for controlling a Mopidy server.

Instruction Scope

SKILL.md instructs the agent to query the Mopidy JSON-RPC endpoint, search the web for canonical rankings when needed, and match results against the local library. The included scripts only call the specified MOPIDY_URL and do not read unrelated system files or environment variables. The 'search the web' step is an agent action (not performed by bundled code) and is reasonable for ranking-based requests.

Install Mechanism

There is no install spec (instruction-only with bundled scripts). No downloads or archive extraction are performed by the skill. Risk is low — the shipped scripts run locally and are human-readable.

Credentials

Only MOPIDY_URL is required, which is appropriate for targeting a Mopidy JSON-RPC endpoint. No unrelated credentials, keys, or system config paths are requested.

Persistence & Privilege

The skill is not marked always:true and does not attempt to modify other skills or system-wide settings. It runs on demand with no elevated persistence.

Assessment

This skill appears to be what it says: a thin controller for a Mopidy JSON-RPC endpoint. Before installing, verify you control the Mopidy host referenced by MOPIDY_URL (the scripts will send JSON-RPC requests there). Ensure curl, jq, and python3 are available. Be aware the SKILL.md suggests doing web searches for canonical track lists — that may cause the agent to call external web services for ranking info (this is separate from the bundled scripts). If your Mopidy endpoint requires authentication, consider how you will provide credentials (avoid embedding secrets in world-readable files). If you do not want the agent to perform web searches for ranking, instruct it not to or disable autonomous invocation for this skill.

Use this skill to control a Mopidy music system through Mopidy's JSON-RPC API in a predictable, scriptable way.

Setup

Configure the Mopidy JSON-RPC endpoint before use.

Recommended environment variable:

export MOPIDY_URL="https://your-mopidy-host.example.com/mopidy/rpc"

Typical endpoint shape:

• https://your-host.example.com/mopidy/rpc

Some installations serve Iris under /iris/, but this skill should control Mopidy through /mopidy/rpc.

Helper scripts:

• scripts/mopidy.sh
• scripts/match_top_tracks.py

Core Tasks

See what is playing

scripts/mopidy.sh current
scripts/mopidy.sh state

See the queue

scripts/mopidy.sh queue

Search for music

scripts/mopidy.sh search "The Beths"
scripts/mopidy.sh search "David Bowie Blackstar"

Use search results to identify the correct URI before adding something.

Add a track or album to the queue

scripts/mopidy.sh add-track backend:song:example
scripts/mopidy.sh add-album backend:album:example

For natural requests like “queue some Beths”, search first, then choose the best matching track or album URI.

List playlists

scripts/mopidy.sh playlists

Add playlist contents to the queue

scripts/mopidy.sh add-playlist-to-queue backend:playlist:example

Playback controls

scripts/mopidy.sh play
scripts/mopidy.sh play-track backend:song:example
scripts/mopidy.sh pause
scripts/mopidy.sh next
scripts/mopidy.sh previous
scripts/mopidy.sh clear

Working Style

• Prefer Mopidy JSON-RPC over UI/browser automation.
• Search first when the request is ambiguous.
• Confirm the selected item if multiple similarly named results exist.
• For queueing requests, default to adding to the queue rather than replacing playback unless the user explicitly asks to play immediately.
• Be careful with destructive queue actions; do not clear or replace the queue unless asked.
• For requests like top, best, essential, greatest, genre-based prompts, or other fuzzy ranking language, do not rely on raw library order alone. First use web search to identify likely canonical songs/albums, then match those items against the local Mopidy library before adding them.
• When using external rankings, report any items that could not be matched locally instead of silently substituting random search results.
• If requested music is not in the library, say so plainly and ask the user rather than substituting random results.

Ranked / Canonical Requests

For prompts like:

• "add the top five The Fall songs"
• "queue the best Bowie tracks"
• "play the essential Brian Eno albums"
• "add 5 of the top indie rock tracks to the queue"

Use this workflow:

1. search the web for a credible ranked, canonical, or genre-representative list
2. extract the song or album names
3. match them against the local Mopidy library
4. add only the confirmed matches to the queue
5. tell the user what was added and what was not found

Use scripts/match_top_tracks.py to help match externally sourced song names against the library.

Playlist Handling

Mopidy playlist APIs and backends can differ.

Safe approach:

1. list playlists
2. identify the target playlist URI
3. look up playlist contents
4. add those track URIs to the queue

Do not assume backend-specific shortcut behavior unless it has been tested on the target Mopidy server.

References

Read references/api-notes.md if you need endpoint details, common Mopidy methods, or URI guidance.