matlab-install-products
Deterministic workflow to download MATLAB Package Manager (mpm) and install MathWorks products from the OS command line with consistent, repeatable behavior. Use when installing MATLAB, Simulink, toolboxes, or support packages via command line, or setting up scripted installations for CI/CD, containers, or fleet provisioning.
npx skills add matlab/matlab-agentic-toolkit --skill matlab-install-products --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Installs MathWorks products by orchestrating a deterministic, command-line workflow using MATLAB Package Manager (mpm). It downloads or uses a canonical mpm binary, prepares a release-specific input file, and runs mpm install with that input, aiming for repeatable, scriptable installations for CI/CD, containers, or fleet provisioning.
How it works
- It defines a deterministic protocol requiring the exact sequence: ensure mpm exists at a canonical path, download and prepare an input file for the requested release, and run the installation using the prepared input.
- It enforces using the canonical OS shell, absolute paths, and a single retry for downloads. If security software blocks execution, it stops and escalates.
- It requires planning and confirmation from the user before execution, including release, destination, products, and dependencies, and provides a plan display for review.
- For Windows, it includes a Windows-specific safety gate: no powershell.exe -Command usage, creation of .ps1 scripts via a Write file tool, and PowerShell execution via -File with elevated privileges when needed.
- It instructs the agent to look up exact product identifiers from the mpm release template and to modify the input file to enable requested products and destination, adding noJRE unless requested.
- The protocol produces scripts such as mpm_download.ps1, mpm_prepare_input.ps1, and mpm_install.ps1, all written to a per-session temporary working folder and executed in order.
When to use it
- When the user wants to install MATLAB, Simulink, toolboxes, or support packages via the command line.
- When a scripted, repeatable MATLAB installation is needed (CI/CD, containers, fleet provisioning).
- When asking about mpm, MATLAB Package Manager, or non-interactive MATLAB installs.
- When adding products to an existing MATLAB installation using mpm.
What it can touch
- It relies on the mpm executable at the canonical path and the working folder for temporary scripts and input files.
- It downloads input templates from MathWorks and edits them to enable the requested products and set destinationFolder and noJRE.
- It executes the mpm install command with the prepared input file.
Caveats
- Determinism contract must be followed exactly; no extra steps or checks beyond those defined.
- Windows steps require carefully created .ps1 scripts via the Write file tool and elevated execution when installing.
- ASCII-only content is required for Windows PowerShell scripts to avoid parse errors.
- If a requested product is not present or destination mismatch occurs during input preparation, the workflow halts per the defined verification steps.
# Installing MATLAB Products with MATLAB Package Manager (mpm) - Deterministic Protocol Use this skill when asked to install MathWorks products using MATLAB Package Manager (mpm) from the OS command line. $ARGUMENTS ## When to Use - User asks to install MATLAB, Simulink, toolboxes, or support packages via the command line - User wants a scripted, repeatable MATLAB installation (CI/CD, containers, fleet provisioning) - User asks about mpm, MATLAB Package Manager, or non-interactive MATLAB installs - User needs to add products to an existing MATLAB installation using mpm ## When NOT to Use - User wants to install via the graphical MATLAB installer or MathWorks website - User is asking about MATLAB licensing or activation (separate workflow) - User wants to manage MATLAB Add-Ons from within MATLAB (use the Add-On Manager) - User needs to install MATLAB Engine API for Python, Java, or C++ (different process) ## Non-Negotiable Determinism Contract (follow exactly) - Follow the steps in **Protocol** in order. Do not add extra steps or checks. - Use **only** the canonical shell for the OS. Do not switch shells. - Use **absolute paths** to `mpm` / `mpm.exe`. Never rely on relative paths. -
- When to Use
- When NOT to Use
- Non-Negotiable Determinism Contract (follow exactly)
- Safety Gate (Windows) — MANDATORY, NO EXCEPTIONS
- Required Inputs (ask only if missing)
- Confirmation Rule
- Plan Display (after confirmation, before execution)
- Execution Style
- Canonical Shell (used throughout the Protocol)
- Pre-Execution Checklist (verify before EVERY Windows step)
- Protocol (exactly 4 steps)
- Step 1 - Ensure mpm exists at canonical path
- Step 2 - Download and edit the release input file
- Step 3 - Run the install command and completion check
mkdir -p "C:/Users/<username>/AppData/Local/Temp/mpm-YYYYMMDD-HHMMSS" test -f "<DESTINATION>/bin/matlab.exe" && echo "VERIFIED" || echo "NOT FOUND" rm -rf "C:/Users/<username>/AppData/Local/Temp/mpm-YYYYMMDD-HHMMSS"
What does the matlab-install-products skill do?
Deterministic workflow to download MATLAB Package Manager (mpm) and install MathWorks products from the OS command line with consistent, repeatable behavior. Use when installing MATLAB, Simulink, toolboxes, or support packages via command line, or setting up scripted installations for CI/CD, containers, or fleet provisioning.
How do I install it?
Run `npx skills add matlab/matlab-agentic-toolkit --skill matlab-install-products --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From matlab/matlab-agentic-toolkit, a repository with 868 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.