Individual skill
music-list
List the account's saved music productions with metadata and audio_url
plugins/ruflo-music/skills/music-list/SKILL.md
Source commit 722232566ad1fc4e73ba4fefc46d77d380ce61ba
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 81,222
- Repository last updated
- Nov 7, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- swarm Repository topic
- agentic-ai Repository topic
- agentic-framework Repository topic
- agentic-workflow Repository topic
- autonomous-agents Repository topic
- codex Repository topic
- mcp-server Repository topic
- multi-agent Repository topic
- ai-assistant Repository topic
- multi-agent-systems Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 1,333 bytes
Read excerpt
# Music List
Surfaces every production in the connected Cognitum Music account.
## When to use
The user asks what tracks exist, wants to find a track by title, or you need a production `id` for `music-get`/`music-stems`/`music-midi`/`music-master` and don't already have it.
## Steps
1. Call `mcp__cogmusic__list_productions({})` — no arguments.
2. Present results sorted by `created_at_unix` descending (the API already returns them this way): title, duration, `id`, and which processing steps have run (`has_stems`/`has_midi`/`has_mastered`).
3. If the user is looking for a specific track, match on `title` (case-insensitive substring) rather than asking them to know the `id` up front.
4. Optionally refresh the `music-productions` memory cache for any entries not already stored there (see `music-generate`'s caching step) — useful after a production was created outside this session (e.g. from the web dashboard).