mpc-plugin-package — Claude Code skill: package and install
The mpc-plugin-package Claude Code skill creates a distributable ZIP for a built MPC plugin, including install instructions. It runs when a plugin needs to be shared, sent out, or prepared for release.
MIT ★ 200 updated 2026-11-07
npx skills add inmusic-software/mpc-plugin-builder-sdk --skill mpc-plugin-package -a claude-codeWhat mpc-plugin-package does
The skill packages an MPC plugin folder into a ZIP with INSTALL.txt and, when present, the project’s README.md. Run python tools/package.py plugins/<Name> to create it. The plugin must first pass a clean build with python tools/build.py plugins/<Name> and no validator errors; testing on an MPC is recommended.
Before release, fill in version, description, author, url, and license in plugin.json. Keep the uid and parameter IDs unchanged across releases. The install guide covers MPC OS 3.10.1 or later, copying files into VST2 Plugins, and enabling external plugin support in the device settings.
What it helps with
- package a built MPC plugin as a distributable ZIP
- include MPC installation steps with the plugin files
- prepare plugin metadata and README for a release
- keep plugin and parameter IDs stable across releases
Example prompts for the agent
- Package the built plugin in
plugins/<Name>for distribution. - Prepare a release ZIP with installation instructions.
- Tell me what needs to be ready before packaging this MPC plugin.
How to install mpc-plugin-package
1Skills CLI (Vercel)
npx skills add inmusic-software/mpc-plugin-builder-sdk --skill mpc-plugin-package -a claude-code2Manually: put the files in place
~/.claude/skills/mpc-plugin-package/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/mpc-plugin-package/
1Skills CLI (Vercel)
npx skills add inmusic-software/mpc-plugin-builder-sdk --skill mpc-plugin-package -a codex2Manually: put the files in place
.agents/skills/mpc-plugin-package/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add inmusic-software/mpc-plugin-builder-sdk --skill mpc-plugin-package -a cursor2Manually: put the files in place
.cursor/skills/mpc-plugin-package/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install inmusic-software/mpc-plugin-builder-sdk .agents/skills/mpc-plugin-package2Manually: put the files in place
.github/skills/mpc-plugin-package/SKILL.md1Skills CLI (Vercel)
npx skills add inmusic-software/mpc-plugin-builder-sdk --skill mpc-plugin-package -a gemini-cli2Platform CLI
gemini skills install https://github.com/inmusic-software/mpc-plugin-builder-sdk --path .agents/skills/mpc-plugin-packageManually: put the files in place
.devin/skills/mpc-plugin-package/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about mpc-plugin-package
How do I install mpc-plugin-package in Claude Code?
Run npx skills add inmusic-software/mpc-plugin-builder-sdk --skill mpc-plugin-package -a claude-code. The skill file is installed at ~/.claude/skills/mpc-plugin-package/SKILL.md.
What does mpc-plugin-package do?
It bundles a built MPC plugin into a ZIP containing the plugin folder and an INSTALL.txt guide. The project’s README.md is included when present.
What must be ready before packaging an MPC plugin?
The plugin needs a clean build from python tools/build.py plugins/<Name> with no validator errors. Fill in version, description, author, url, and license in plugin.json before release.
Source text
SKILL.md · MIT
--- name: mpc-plugin-package description: Package a built MPC plugin into a distributable zip with installation instructions for MPC owners. Use when the user wants to share, release, publish, upload or send their plugin, or asks how others install it. --- # Package for distribution Prerequisite: a clean build (`python tools/build.py plugins/<Name>` with no validator errors) and ideally a pass on the MPC itself. ``` python tools/package.py plugins/<Name> ``` Produces `plugins/<Name>/dist/<slug>-<version>-mpc.zip` containing: - `<Manufacturer> - VST - <Name>/` the complete plugin folder (both ARM builds, plugin.json, version.xml, Plugin Skins, Content) - `INSTALL.txt` step-by-step install instructions for non-technical users (requires MPC OS 3.10.1 or later; copy to `VST2 Plugins` on a drive; enable VST plugins on the device via Preferences → Enhancements (Beta) → Enable Enhancements + External Plugin Support; find it under External Plugins; warnings; how to uninstall) - the project's `README.md` if present Before packaging: 1. Set `version` in `plugin.json` (semantic: `1.0.0`, bump for every release) and make sure `description`, `author`, `url` and `license` keys are filled; INSTALL.txt uses them. 2. Make the project `README.md` useful to players: what it does, parameter list by page, tips, known limits, licence, credits for any DSP code you borrowed. 3. Never change `uid` or parameter ids between releases. Hand the zip path to the user and summarise what is inside. If they want to publish, suggest a GitHub release with the zip attached and the README as the release notes.
© inmusic-software · MIT · inmusic-software/mpc-plugin-builder-sdk