| name | flstudio-production |
| description | Use this skill whenever the user wants to control FL Studio from Claude — write or trigger drum patterns, set tempo, change mixer levels, write notes to the Piano Roll, work with Carnatic ragas or kuthu rhythms in FL Studio, or troubleshoot the FLStudioMCP bridge. Trigger on FL Studio, FL, Fruity Loops, FLStudioMCP, "FL-il pannu", music production via Claude. ALWAYS use the fl-studio MCP server tools — never instruct the user to perform the change manually if a tool exists. |
FL Studio production skill
This is the orchestration layer. Deep content lives in references/.
Before you act
- Call
fl_ping once at the start of every session. If alive: false,
stop and tell the user to open FL Studio and select FLStudioMCP as a
controller type. Do not retry blindly.
- Read
references/limits.md so you don't promise things the FL API can't
deliver (no plugin loading, no new-pattern creation, etc).
- If the user is going to write Piano Roll notes, FL Studio must be the
focused window. Warn them once at the start.
Tool selection
| User intent | Tools |
|---|
| Tempo, play, stop | fl_set_tempo, fl_play, fl_stop, fl_toggle_play |
| Where are we in the song | fl_get_song_position |
| Drum patterns | fl_channel_set_grid_bit (Phase 1) — NOT the Piano Roll |
| Mixer levels | fl_mixer_set_volume, _set_pan (Phase 2) |
| Melody in a raga | fl_preset_write_raga_melody (Phase 6) which calls Piano Roll under the hood |
| Kuthu beat | fl_preset_write_kuthu_pattern (Phase 6) |
When something fails
FLNotRunning → bridge is healthy, FL is not. Ask user to open FL.FLTimeout → controller is loaded but stalled. Ask user to re-select
FLStudioMCP in MIDI Settings.FLCommandFailed with code=client → bad input. Show the user what was
wrong and ask for a correction.
References
references/limits.md — FL API constraints.references/ragas.md — How the Carnatic raga preset pack is organised.references/kuthu.md — Kuthu / gaana rhythm vocabulary.
(These references are written as Phase 6 ships.)
