Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →matlab/matlab-install-products
Deterministic workflow to download MATLAB Package Manager (mpm) and install MathWorks products from the OS command line with consistent, repeatable behavior.
Passed 21 of 25 test cases with the skill, and 11 of 25 without it.
and 8 more in the full report
10 fixed11 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
I am configuring an mpm input file for MATLAB R2025b at /usr/local/matlab/R2025b on Linux. I want to prevent mpm from bundling the Java Runtime Environment. What line should be added to the input file?
| Checked | Without skill | With skill |
|---|---|---|
| Configures noJRE=true on its own line after destinationFolder in the input file. | Missed | Passed |
The instructions your model reads when the skill loads.
Use this skill when asked to install MathWorks products using MATLAB Package Manager (mpm) from the OS command line.
$ARGUMENTS
mpm / mpm.exe. Never rely on relative paths.STOP. Read this entire section before executing ANY Windows step.
NEVER use powershell.exe -Command for ANY reason. Bash mangles $, backticks, quotes, arrays, and script blocks before PowerShell sees them. This WILL cause unexpected EOF or syntax errors.
NEVER create any file with a bash heredoc (cat > file <<'EOF' ... EOF) or shell redirection (echo ... > file, printf ... > file, >>). This includes quoted heredocs (<<'PS1', <<"EOF"). Do not rationalize an exception: the reason is NOT variable expansion (so "the delimiter is quoted, so it's safe" is wrong). The reasons the ban is absolute are (a) Git Bash rewrites paths, line endings, and encoding as it creates the file, corrupting .ps1 parsing, and (b) the Write file tool is the single approved mechanism for creating any file in this protocol — scripts and input files alike. There is no safe heredoc. If you catch yourself reaching for cat, echo, printf, >, >>, or << to produce a file, STOP and use the Write file tool.
ALWAYS write .ps1 files using the Write file tool, then invoke with:
powershell.exe -NoLogo -NoProfile -NonInteractive -ExecutionPolicy Bypass -File <absolute-script-path>
Do not emit CMD-only syntax (if not exist, set VAR=, %USERPROFILE%). Use PowerShell equivalents (Test-Path, $env:USERPROFILE).
ASCII only in all .ps1 file content. No em dashes (—), en dashes (–), curly quotes, or other non-ASCII characters. They cause PowerShell parse errors (broken string terminators, missing brace errors) when file encoding doesn't preserve them.
If you are about to type powershell.exe -Command — STOP. You are violating this rule. Use the Write file tool to create a .ps1 file instead.
test cases passed, vs 11 / 25 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.