Extract MIDI or a score from an already generated music production using pitch tracking. The skill checks that MIDI is available and directs users to the dashboard for downloading it for transcription, arranging, or music software import.
Extract MIDI/score from an existing production
This skill uses pitch tracking to extract MIDI or a score from music that has already been generated. It takes a production-id, which identifies an existing production, and runs extraction through mcp__cogmusic__extract_midi. It then checks the production with mcp__cogmusic__get_production and confirms that has_midi, the field indicating MIDI availability, has become true.
Use it when you want to transcribe a generated track or use MIDI as material for an arrangement. It also helps when you want to import generated music into a DAW, or digital audio workstation, for further music production. The process covers running extraction, checking the result, and explaining where to obtain the file.
production-id.”You need an existing production id and the listed MCP tools. Extraction involves actual GPU processing. One retry is suggested for a temporary failure. The MIDI file itself is not included in the MCP response; download it from the dashboard.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI rated this skill on four points using only the contents of its SKILL.md. Stars and popularity are not taken into account.
The total counts each point as A = 25, B = 15, C = 5. Rated by AI (OpenAI Codex) as of Oct 21, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
Runs pitch-tracked MIDI/score extraction on an already-generated production.
The user wants a MIDI file or score from a track they've already generated (transcription, arranging, DAW import). Needs an existing production id.
mcp__cogmusic__extract_midi({ id: "<production-id>" }). Real GPU work, same reliability profile as music-stems and music-generate — one retry on a transient failure is reasonable before treating it as broken.mcp__cogmusic__get_production that has_midi is now true.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Compare models available through the HuggingFace router with chat-ui configuration, research missing models, and write short English descriptions of their architecture and capabilities. Add entries to both production and development configuration files and commit the changes.
Create an Architecture Decision Record, a document for recording important design choices, with the next sequential number. It generates a Markdown template, registers the record in AgentDB, and links related decisions found through search.
Build a searchable index and relationship graph from ADRs, records of architectural decisions. Import two supported document formats, refresh existing metadata without duplicate relationships, and review summaries of statuses, missing references, and inconsistencies.
Rebuild the index of ADRs, records of architectural decisions, after files or relationship lines are deleted. It clears stored records and relationships, indexes the files still present, and checks that the final record count matches.
Review code changes against accepted Architecture Decision Records, documents that capture agreed design choices. Report violations, outdated references, compliant changes, and areas without ADR coverage, then suggest code fixes or a new decision record where appropriate.
Check saved architecture decision records (ADRs) for broken references, circular replacement relationships, and inconsistent statuses. Use the results to verify imported records or stop a CI check when selected integrity rules fail.