FL Studio Scripting
PassAudited by ClawScan on May 1, 2026.
Overview
This is a documentation-only FL Studio scripting reference; its main risks are expected project/hardware control and continuously running controller scripts, not hidden behavior.
This skill appears safe as a reference, but treat any FL Studio script or PyFLP automation it helps generate as code that can modify your project. Review the script, run it only on intended files, and keep backups of important FLP projects.
Findings (2)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
A script produced using this reference could alter mixer, channel, MIDI, or project-file state if the user runs it.
The skill is intended to help create scripts and macros that can modify FL Studio projects and save files. This is purpose-aligned, but users should understand that generated scripts may change creative work.
Use for programmatic configuration, device customization, MIDI transport, macros, and save file manipulation.
Review generated scripts, confirm the exact target project/tracks/files, and back up important FLP files before running automation.
An installed controller script may continue processing MIDI and FL Studio events during the FL Studio session.
The artifacts disclose a long-running script mode. Continuous operation is expected for MIDI controller scripts, but it means installed scripts can keep responding to events until disabled or FL Studio closes.
MIDI Controller Scripting ... Runs: Continuously while FL Studio is open.
Only install reviewed controller scripts, include cleanup logic such as OnDeInit where appropriate, and remove or disable scripts that are no longer needed.