How do I install the Edit Flp Project skill?

Run npx skillmds@latest add jihadkhawaja/edit-flp-project in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Edit Flp Project safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Edit Flp Project?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Edit Flp Project free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Edit Flp Project?

jihadkhawaja (@jihadkhawaja) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Edit Flp Project by jihadkhawaja — Agent Skill

Name: Edit Flp Project
Author: jihadkhawaja

Edit Flp Project

Safely edit, revise, remix, rename, or rearrange an existing FL Studio FLP with Music2DAW. Use for changing notes, tempo, playlist clips, channel names, FLEX states, routing, mixer levels, stereo image, or mastering while preserving the source.

jihadkhawaja f0d7df6 2.6 KB Updated Sep 17, 2026

File contents

Edit FLP Project

Procedure

Read the AI-first workflow.
Choose one execution mode for the task: MCP tools when the music2daw server is connected, otherwise the Music2DAW CLI. Use music2daw when the release bundle is installed; in a source checkout, use dotnet run --project src/Music2Daw.Cli -- in its place.
Inspect the exact input FLP with MCP inspect_flp or CLI music2daw inspect <input.flp>. Capture tempo, PPQ, IDs, note counts, playlist count, plugin-state hashes, text hints, and sequence-risk warnings.
State a narrow musical hypothesis and one observable check before editing.
Create a new versioned output path. Never overwrite the source FLP.
Express edits in a checked-in edit-request.json. Pass its content to MCP edit_flp, or pass its path to CLI music2daw edit <source.flp> <output.flp> <request.json>.
Apply one coherent edit slice, inspect it with the same mode, and compare structural invariants before widening scope.
For instrument replacement, copy the full plugin-state bundle (DataNewPlugin plus DataPluginParams) from an existing channel via pluginStateCopies, and rename the target separately. Verify both pluginInitializationSha256 and pluginSettingsSha256 match the source afterward. For guaranteed audible results, also route the musical notes to the known-good source channel and leave the copied target silent at volume 0 with no notes.
Before assigning written melody or harmony to a copied state, reject isLikelySequenced sources unless the internal sequence is intentional.
For note replacement, preserve target-channel note metadata and verify there are no ghost notes.
In a source checkout, run focused tests after parser/editor changes and dotnet test before completion.
Launch the derivative FLP and report its path, process ID, execution mode, verified changes, and remaining audible checks.

Safety Gates

Reject source and output paths that are equal.
Preserve unknown events and opaque plugin bytes byte-for-byte.
Do not claim an audible mix or mastering result from metadata alone; identify what still needs listening in FL Studio.
If an event is missing, fail explicitly instead of claiming the edit succeeded.
Validate FL Studio 25 playlist records after playlist code changes.

---name: edit-flp-projectdescription: Safely edit, revise, remix, rename, or rearrange an existing FL Studio FLP with Music2DAW. Use for changing notes, tempo, playlist clips, channel names, FLEX states, routing, mixer levels, stereo image, or mastering while preserving the source.---# Edit FLP Project## Procedure1. Read [the AI-first workflow](../../../docs/AI_FIRST_FLP_WORKFLOW.md).2. Choose one execution mode for the task: MCP tools when the `music2daw` server is connected, otherwise the Music2DAW CLI. Use `music2daw` when the release bundle is installed; in a source checkout, use `dotnet run --project src/Music2Daw.Cli --` in its place.3. Inspect the exact input FLP with MCP `inspect_flp` or CLI `music2daw inspect <input.flp>`. Capture tempo, PPQ, IDs, note counts, playlist count, plugin-state hashes, text hints, and sequence-risk warnings.4. State a narrow musical hypothesis and one observable check before editing.5. Create a new versioned output path. Never overwrite the source FLP.6. Express edits in a checked-in `edit-request.json`. Pass its content to MCP `edit_flp`, or pass its path to CLI `music2daw edit <source.flp> <output.flp> <request.json>`.7. Apply one coherent edit slice, inspect it with the same mode, and compare structural invariants before widening scope.8. For instrument replacement, copy the full plugin-state bundle (`DataNewPlugin` plus `DataPluginParams`) from an existing channel via `pluginStateCopies`, and rename the target separately. Verify both `pluginInitializationSha256` and `pluginSettingsSha256` match the source afterward. For guaranteed audible results, also route the musical notes to the known-good source channel and leave the copied target silent at volume 0 with no notes.9. Before assigning written melody or harmony to a copied state, reject `isLikelySequenced` sources unless the internal sequence is intentional.10. For note replacement, preserve target-channel note metadata and verify there are no ghost notes.11. In a source checkout, run focused tests after parser/editor changes and `dotnet test` before completion.12. Launch the derivative FLP and report its path, process ID, execution mode, verified changes, and remaining audible checks.## Safety Gates- Reject source and output paths that are equal.- Preserve unknown events and opaque plugin bytes byte-for-byte.- Do not claim an audible mix or mastering result from metadata alone; identify what still needs listening in FL Studio.- If an event is missing, fail explicitly instead of claiming the edit succeeded.- Validate FL Studio 25 playlist records after playlist code changes.

Frequently asked questions