[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75MFW17FDH4X6P3P0DDFFDH":3,"skill-same:01M75MFW17FDH4X6P3P0DDFFDH":66},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":29,"commitSha":30,"skillDirectory":31,"forksCount":32,"repositoryHtmlUrl":33,"repositoryHomepageUrl":6,"ownerHtmlUrl":34,"ownerBlogUrl":35,"ownerDescription":6,"updatedAt":36,"install":37,"resources":50},"01M75MFW17FDH4X6P3P0DDFFDH","matlab-install-products",null,"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\u002FCD, containers, or fleet provisioning.","stanfish06\u002Fskillquarium","stanfish06","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F93099613?v=4","01M75F1CK4ZW109ZK3T26VN52F","Zhiyuan","01M75F1CM53VH6F79DZ8GXKKES",12,"BSD-2-Clause","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fmatlab-install-products\u002FLICENSE.md","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fmatlab-install-products\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: matlab-install-products\ndescription: \"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\u002FCD, containers, or fleet provisioning.\"\nlicense: \"MathWorks BSD-3-Clause\"\nmetadata:\n  author: MathWorks\n  version: \"1.3\"\n---\n\n# Installing MATLAB Products with MATLAB Package Manager (mpm) - Deterministic Protocol\n\nUse this skill when asked to install MathWorks products using MATLAB Package Manager (mpm) from the OS command line.\n\n$ARGUMENTS\n\n## When to Use\n\n- User asks to install MATLAB, Simulink, toolboxes, or support packages via the command line\n- User wants a scripted, repeatable MATLAB installation (CI\u002FCD, containers, fleet provisioning)\n- User asks about mpm, MATLAB Package Manager, or non-interactive MATLAB installs\n- User needs to add products to an existing MATLAB installation using mpm\n\n## When NOT to Use\n\n- User wants to install via the graphical MATLAB installer or MathWorks website\n- User is asking about MATLAB licensing or activation (separate workflow)\n- User wants to manage MATLAB Add-Ons from within MATLAB (use the Add-On Manager)\n- User needs to install MATLAB Engine API for Python, Java, or C++ (different process)\n\n## Non-Negotiable Determinism Contract (follow exactly)\n- Follow the steps in **Protocol** in order. Do not add extra steps or checks.\n- Use **only** the canonical shell for the OS. Do not switch shells.\n- Use **absolute paths** to `mpm` \u002F `mpm.exe`. Never rely on relative paths.\n- Retry downloads at most **once**. Otherwise stop and report the error.\n- If security software blocks execution: **stop** and instruct escalation. Do not bypass.\n\n## Safety Gate (Windows) — MANDATORY, NO EXCEPTIONS\n\n**STOP. Read this entire section before executing ANY Windows step.**\n\n1. **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.\n2. **NEVER** use bash heredoc syntax (`cat > file \u003C\u003C'EOF'`) or bash redirection (`echo ... >`) to create PowerShell scripts.\n3. **ALWAYS** write `.ps1` files using the **Write file tool**, then invoke with:\n   `powershell.exe -NoLogo -NoProfile -NonInteractive -ExecutionPolicy Bypass -File \u003Cabsolute-script-path>`\n4. Do not emit CMD-only syntax (`if not exist`, `set VAR=`, `%USERPROFILE%`). Use PowerShell equivalents (`Test-Path`, `$env:USERPROFILE`).\n\n5. **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.\n\n**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.**\n\nWindows script authoring pattern:\n- **WRONG**: `powershell.exe -Command \"$script = @'...`  (bash corrupts `$` and heredocs)\n- **WRONG**: `cat > C:\u002FWindows\u002FTemp\u002Fscript.ps1 \u003C\u003C'PS1' ... PS1`  (bash heredoc, breaks on Windows)\n- **CORRECT**: create a unique temp folder, use the **Write file tool** to write `.ps1` files into it, then run with `-File`\n\nUnique temp folder:\n- Before Step 1, create a timestamped working folder using the Bash tool:\n  - Windows: `mkdir -p \"C:\u002FUsers\u002F\u003Cusername>\u002FAppData\u002FLocal\u002FTemp\u002Fmpm-\u003CYYYYMMDD-HHMMSS>\"`\n  - Linux\u002FmacOS: `mkdir -p \"\u002Ftmp\u002Fmpm-\u003CYYYYMMDD-HHMMSS>\"`\n- Use this folder for ALL generated scripts and input files throughout the protocol\n- Because the folder is new, the Write file tool can always create files in it without needing to delete anything first\n- Delete the entire folder during the final cleanup step\n\nWindows PowerShell syntax reminders:\n- Bad: `if not exist C:\\Users\\name\\Downloads mkdir C:\\Users\\name\\Downloads` (CMD syntax)\n- Good: `if (-not (Test-Path -LiteralPath 'C:\\Users\\name\\Downloads')) { New-Item -ItemType Directory -Path 'C:\\Users\\name\\Downloads' | Out-Null }`\n\nDo not ask the user for the exact product name or identifier. Look it up using the appropriate mpm input file from https:\u002F\u002Fwww.mathworks.com\u002Fproducts\u002Fmpm.html\nDo not ask the user whether to install dependencies or not. mpm will take care of it. Just install whatever the user asked for, and let mpm do the rest.\nIf a user types the shortname of MATLAB releases, automatically use the correct expanded full name. e.g. 25a is R2025a, 25b is R2025b\n\n## Required Inputs (ask only if missing)\n1. Operating system (Windows, Linux, macOS)\n2. MATLAB release (for example `R2025b`)\n3. Installation destination (absolute path)\n4. Requested products \u002F toolboxes \u002F support packages\n\n## Confirmation Rule\nBefore executing any steps, always confirm the user's choices:\n- Release\n- Destination folder\n- Products\n- Support packages\n\nAsk for confirmation in one message. The user can reply `yes to all` to confirm everything at once. If they reply with specific changes, update the selections and confirm again.\nDisplay each value to be confirmed in its own new line.\nNote at the bottom of the confirmation message: \"Required dependencies will be installed automatically by mpm.\"\n\n## Plan Display (after confirmation, before execution)\n\nOnce the user confirms their inputs, display a clear installation plan before running any commands. Adapt the template below for the target OS (use forward slashes and `\u002Ftmp\u002F` for Linux\u002FmacOS, omit `.ps1` script references, and omit the UAC note). Use this format:\n\n```\nHere's what I'll do:\n\nWorking folder: \u003CC:\\Users\\\u003Cusername>\\AppData\\Local\\Temp\\mpm-YYYYMMDD-HHMMSS>\n\nStep 1 — Download mpm\n  Check for mpm at \u003Ccanonical mpm path>\n  Download from \u003CURL> if not present\n  Script: \u003Cworking folder>\\mpm_download.ps1\n\nStep 2 — Prepare input file\n  Download release template for \u003Crelease> from mathworks.com\n  Set destination folder: \u003Cdestination>\n  Enable products: \u003Ccomma-separated list>\n  Input file: \u003Cworking folder>\\mpm_input_\u003Creleaselower>.txt\n  Script: \u003Cworking folder>\\mpm_prepare_input.ps1\n\nStep 3 — Run installation\n  Execute mpm install using the prepared input file\n  \u003CWindows only: note that elevated permissions (UAC prompt) will be required>\n\nStep 4 — Verify\n  Confirm MATLAB binary exists: \u003Ccompletion artifact path>\n  Verify products via: \u003CDESTINATION>\u002Fappdata\u002Fprodcontents.json\n  \u003Cif support packages requested> Verify support packages via: \u003CSUPPORTPKGROOT>\u002Fappdata\u002Fprodcontents.json\n  Delete working folder: \u003Cworking folder>\n  \u003Cif MATLAB included> Show release notes: https:\u002F\u002Fwww.mathworks.com\u002Fhelp\u002Fmatlab\u002Frelease-notes.html?startrelease=\u003CRELEASE>&endrelease=\u003CRELEASE>\n```\n\nResolve all environment variables and shell-specific paths to absolute paths before displaying. Generate the timestamp for the working folder name at plan display time so it is fixed for the entire session.\nDo not start Step 1 until the user acknowledges the plan (a simple \"ok\", \"go\", \"yes\", or similar is enough).\n\nOfficial documentation:\n- Get mpm: https:\u002F\u002Fwww.mathworks.com\u002Fhelp\u002Finstall\u002Fug\u002Fget-mpm-os-command-line.html\n- mpm install: https:\u002F\u002Fwww.mathworks.com\u002Fhelp\u002Finstall\u002Fug\u002Fmpminstall.html\n\n## Execution Style\n\n> **Important:** When executing steps, do not narrate or explain what you are about to do. Just run the commands and report results concisely (success, failure, or error). Reserve commentary for confirmations, the plan display, and error reporting only.\n\n## Canonical Shell (used throughout the Protocol)\n- **Windows**: Windows PowerShell (`powershell.exe`)\n- **Linux**: `bash` \u002F `sh`\n- **macOS**: `zsh` or `bash` (Apple silicon only; Intel Mac is not supported — stop and inform the user)\n\n## Pre-Execution Checklist (verify before EVERY Windows step)\n\nBefore running any command in Steps 1–3 on Windows, confirm:\n- [ ] The PowerShell script was written using the **Write file tool** (not `-Command`, not heredoc, not `echo`)\n- [ ] The script is invoked with `powershell.exe ... -File \u003Cpath>` (not `-Command`)\n- [ ] No PowerShell code appears inline in any `bash` command\n\nIf any check fails, STOP and rewrite using the Write file tool.\n\n## Protocol (exactly 4 steps)\n\n### Step 1 - Ensure mpm exists at canonical path\n\nCanonical locations (resolve to absolute paths before use):\n- Windows: `\u003Cuser home>\\Downloads\\mpm.exe`\n- Linux: `\u003Cuser home>\u002FDownloads\u002Fmpm`\n- macOS: `\u003Cuser home>\u002FDownloads\u002Fmpm`\n\nIf the file exists at that path, reuse it. Otherwise download from:\n- Windows: https:\u002F\u002Fwww.mathworks.com\u002Fmpm\u002Fwin64\u002Fmpm\n- Linux: https:\u002F\u002Fwww.mathworks.com\u002Fmpm\u002Fglnxa64\u002Fmpm\n- macOS: https:\u002F\u002Fwww.mathworks.com\u002Fmpm\u002Fmaca64\u002Fmpm\n\n#### Windows (PowerShell)\n\n**MANDATORY: Use the Write file tool to create this script. NEVER use -Command or heredoc.**\n\n1. Create the working folder with the Bash tool (use the timestamp fixed at plan display time):\n\n```bash\nmkdir -p \"C:\u002FUsers\u002F\u003Cusername>\u002FAppData\u002FLocal\u002FTemp\u002Fmpm-YYYYMMDD-HHMMSS\"\n```\n\n2. Use the **Write file tool** to write the following content to `\u003Cworking folder>\\mpm_download.ps1`:\n\n```powershell\nparam(\n  [Parameter(Mandatory = $true)]\n  [string]$Destination\n)\nif (Test-Path -LiteralPath $Destination) {\n  Write-Host \"mpm already present at $Destination\"\n} else {\n  Write-Host \"Downloading mpm from https:\u002F\u002Fwww.mathworks.com\u002Fmpm\u002Fwin64\u002Fmpm - this may take a few minutes...\"\n  Invoke-WebRequest -Uri \"https:\u002F\u002Fwww.mathworks.com\u002Fmpm\u002Fwin64\u002Fmpm\" -OutFile $Destination -UseBasicParsing\n  if (-not (Test-Path -LiteralPath $Destination)) { throw \"mpm download failed: $Destination\" }\n  Write-Host \"mpm downloaded to $Destination\"\n}\n```\n\n3. Run it:\n\n```bash\npowershell.exe -NoLogo -NoProfile -NonInteractive -ExecutionPolicy Bypass -File \"\u003Cworking folder>\\mpm_download.ps1\" -Destination \"C:\\Users\\\u003Cusername>\\Downloads\\mpm.exe\"\n```\n\n#### Linux\u002FmacOS\n\nSee `reference\u002Flinux-macos-steps.md` for full shell scripts. Summary: create working folder at `\u002Ftmp\u002Fmpm-YYYYMMDD-HHMMSS`, download mpm with `curl -fL -o` to `~\u002FDownloads\u002Fmpm`, and `chmod +x`.\n\n### Step 2 - Download and edit the release input file\n\nAlways use a release template input file from:\nhttps:\u002F\u002Fwww.mathworks.com\u002Fproducts\u002Fmpm.html\n\nDownload the template input file for the requested release, then edit it:\n- Uncomment and set `destinationFolder` to the requested installation path.\n- Uncomment each `product.\u003CName>` line for requested products and support packages.\n- Add `noJRE=true` to the input file (on its own line, after `destinationFolder`). This prevents mpm from bundling a Java Runtime. Only omit this line if the user explicitly requests JRE installation.\n- Leave `updateLevel` commented unless the user requests a specific update.\n- Do not edit the checksum line (`?checksum=...`).\n\nAfter editing the file, verify:\n- The input file exists at the expected path.\n- `destinationFolder` matches the user-requested install path exactly.\n- Each requested `product.\u003CName>` line is uncommented (no leading `#`).\n- Non-requested products remain commented out.\n\nIf any verification fails, stop and retry the download once, then re-edit and re-verify.\nIf it still fails, stop and report the error.\n\nThe input file format uses `product.\u003CName>` entries for both products and support packages.\nYou must look up the exact `product.\u003CName>` identifiers in the release input file.\nProduct identifiers use underscores for spaces (e.g. \"Signal Processing Toolbox\" -> `product.Signal_Processing_Toolbox`).\n\n- Always display the full path to the ps1 script that was generated\n\n#### Windows (PowerShell)\n\n**MANDATORY: Use the Write file tool to create this script. NEVER use -Command or heredoc.**\n\n1. Use the **Write file tool** to write the following content to `\u003Cworking folder>\\mpm_prepare_input.ps1`:\n\n```powershell\nparam(\n  [Parameter(Mandatory = $true)]\n  [string]$Release,\n  [Parameter(Mandatory = $true)]\n  [string]$Destination,\n  [Parameter(Mandatory = $true)]\n  [string]$WorkingFolder,\n  [Parameter(Mandatory = $true)]\n  [string]$Products\n)\n\nSet-StrictMode -Version Latest\n$ErrorActionPreference = \"Stop\"\n\n# -File mode passes \"a,b\" as one string; split into an array\n$ProductList = $Products -split ',' | ForEach-Object { $_.Trim() }\n\n$releaseLower = $Release.ToLower()\n$inputUrl  = \"https:\u002F\u002Fwww.mathworks.com\u002Fcontent\u002Fdam\u002Fmathworks\u002Fmathworks-dot-com\u002Fproducts\u002Fmpm\u002Fmpm-input-${releaseLower}.txt\"\n$inputFile = Join-Path $WorkingFolder \"mpm_input_${releaseLower}.txt\"\n\nWrite-Host \"Downloading input file from $inputUrl...\"\nInvoke-WebRequest -Uri $inputUrl -OutFile $inputFile -UseBasicParsing\nif (-not (Test-Path -LiteralPath $inputFile)) {\n  throw \"Input file was not downloaded: $inputFile\"\n}\n\n$lines = Get-Content -LiteralPath $inputFile\n\n$lines = $lines | ForEach-Object {\n  if ($_ -match '^\\s*#?\\s*destinationFolder=') {\n    \"destinationFolder=$Destination\"\n    \"noJRE=true\"\n  }\n  else {\n    $_\n  }\n}\n\nforeach ($product in $ProductList) {\n  $escaped = [Regex]::Escape($product)\n  $lines = $lines | ForEach-Object {\n    if ($_ -match \"^\\s*#\\s*$escaped\\s*$\") {\n      $product\n    }\n    else {\n      $_\n    }\n  }\n}\n\nSet-Content -LiteralPath $inputFile -Value $lines -Encoding UTF8\n\n$lines = Get-Content -LiteralPath $inputFile\n\n$destinationLine = $lines | Where-Object { $_ -match '^destinationFolder=' } | Select-Object -First 1\nif (-not $destinationLine) { throw \"destinationFolder line not found in $inputFile\" }\nif ($destinationLine -ne \"destinationFolder=$Destination\") { throw \"destinationFolder mismatch: $destinationLine\" }\n\n$uncommentedProducts = $lines | Where-Object { $_ -match '^\\s*product\\.' }\n$unexpectedProducts  = $uncommentedProducts | Where-Object { $ProductList -notcontains $_ }\nif ($unexpectedProducts) { throw \"Unrequested products enabled: $($unexpectedProducts -join ', ')\" }\n\nforeach ($product in $ProductList) {\n  if (-not ($lines -contains $product)) { throw \"Requested product not enabled: $product\" }\n}\n\nWrite-Host \"Input file ready: $inputFile\"\n```\n\nNote: the script writes the input file to `\u003Cworking folder>\\mpm_input_\u003Creleaselower>.txt`, so cleanup of the working folder deletes it automatically. The input file path will be reported by the script on completion.\n\n2. Run it (substitute actual working folder, release, destination, and product identifiers):\n\n```bash\npowershell.exe -NoLogo -NoProfile -NonInteractive -ExecutionPolicy Bypass -File \"\u003Cworking folder>\\mpm_prepare_input.ps1\" -Release \"R2025b\" -Destination \"C:\\MATLAB\\R2025b\" -WorkingFolder \"\u003Cworking folder>\" -Products \"product.MATLAB,product.Simulink\"\n```\n\n#### Linux\u002FmacOS\n\nSee `reference\u002Flinux-macos-steps.md` for the full shell script. Summary: download the release input file with `curl`, edit with `sed` to set `destinationFolder` and uncomment requested products, then verify all edits.\n\n- Do not delete generated files yet; cleanup happens after Step 3.\n\n### Step 3 - Run the install command and completion check\n\n**IMPORTANT:**\n- When using `--inputfile`, do not pass any other mpm options.\n- Windows requires elevation. Use `Start-Process -Verb RunAs` for elevated execution.\n- Always display the fully expanded command before running it.\n- Substitute actual values for release, working folder, and destination in the snippets below.\n\n#### Windows\n\n**MANDATORY: Use the Write file tool to create a .ps1 script for this step. NEVER use -Command or heredoc. Then invoke with `powershell.exe ... -File \u003Cpath>`.**\n\nWrite the following to `\u003Cworking folder>\\mpm_install.ps1` using the **Write file tool**, then run with `-File`:\n\n```powershell\nparam(\n  [Parameter(Mandatory = $true)]\n  [string]$MpmPath,\n  [Parameter(Mandatory = $true)]\n  [string]$InputFile\n)\n\n$installArgs = @(\n  \"install\",\n  \"--inputfile=$InputFile\"\n)\n\n$display = '\"' + $MpmPath + '\" install ' + ('--inputfile=\"' + $InputFile + '\"')\nWrite-Host \"Running: $display\"\n\nStart-Process -FilePath $MpmPath -ArgumentList $installArgs -Verb RunAs -Wait\n```\n\nRun it:\n\n```bash\npowershell.exe -NoLogo -NoProfile -NonInteractive -ExecutionPolicy Bypass -File \"\u003Cworking folder>\\mpm_install.ps1\" -MpmPath \"C:\\Users\\\u003Cusername>\\Downloads\\mpm.exe\" -InputFile \"\u003Cworking folder>\\mpm_input_\u003Creleaselower>.txt\"\n```\n\n#### Linux\u002FmacOS\n\nSee `reference\u002Flinux-macos-steps.md`. Summary: run `mpm install --inputfile=\u003Cpath>` directly (no elevation needed).\n\n### Step 4 - Verification\n\nThis step defines **completion**. It is mandatory.\nWait until the mpm process has exited. Do not proceed until it is done.\nIf the completion artifact does not exist, stop and report failure. **Do not re-run Step 3.**\n\nCompletion artifacts (use the destination folder you set in the input file):\n- **Windows**: `\u003CDESTINATION>\\bin\\matlab.exe`\n- **Linux**: `\u003CDESTINATION>\u002Fbin\u002Fmatlab`\n- **macOS**: `\u003CDESTINATION>\u002FContents\u002FMacOS\u002FMATLAB`\n\nUse the Bash tool with `test -f` to check existence. Do **not** use `powershell.exe -Command` for this check.\n\n```bash\ntest -f \"\u003CDESTINATION>\u002Fbin\u002Fmatlab.exe\" && echo \"VERIFIED\" || echo \"NOT FOUND\"\n```\n\n#### Per-item verification\n\nAfter confirming the MATLAB binary exists, verify each requested item was installed. Products and support packages are stored in **separate locations** with separate `prodcontents.json` files. Do not check one location for items that belong in the other.\n\n**Products** (items whose mpm identifier does NOT contain `Support_Package`):\n- Read `\u003CDESTINATION>\u002Fappdata\u002Fprodcontents.json` using the Read tool.\n- This is a JSON object. Keys are product names with version and platform tokens (e.g. `\"Simulink 25.1 win64\"`).\n- For each requested product, check that a key exists whose name starts with the product's display name (strip the `product.` prefix and replace underscores with spaces). For example, `product.Signal_Processing_Toolbox` matches a key starting with `Signal Processing Toolbox`.\n\n**Support packages** (items whose mpm identifier contains `Support_Package`):\n- Derive the support package root based on platform:\n  - **Windows:** `C:\\ProgramData\\MATLAB\\SupportPackages\\\u003CRELEASE>`\n  - **Linux:** `\u002Fusr\u002Flocal\u002FMATLAB\u002FSupportPackages\u002F\u003CRELEASE>`\n  - **macOS:** `~\u002FLibrary\u002FApplication Support\u002FMathWorks\u002FMATLAB\u002FSupportPackages\u002F\u003CRELEASE>`\n- Read `\u003CSUPPORTPKGROOT>\u002Fappdata\u002Fprodcontents.json` using the Read tool.\n- If the file does not exist, the support package installation failed. Report failure.\n- For each requested support package, check that a matching key exists (same name mapping as products above).\n\nReport **Verified** or **Not found** for each item. If any item is not found, stop and report which items failed.\n\nAfter all items are verified, delete the entire working folder and its contents using the Bash tool:\n\n```bash\nrm -rf \"C:\u002FUsers\u002F\u003Cusername>\u002FAppData\u002FLocal\u002FTemp\u002Fmpm-YYYYMMDD-HHMMSS\"\n```\n\n#### Release Notes Link\n\nOnly if MATLAB (the base product) was included in the installation, provide a link to the release notes after successful verification and cleanup:\n\n```\nhttps:\u002F\u002Fwww.mathworks.com\u002Fhelp\u002Fmatlab\u002Frelease-notes.html?startrelease=\u003CRELEASE>&endrelease=\u003CRELEASE>&rntext=&groupby=release&sortby=descending&searchHighlight=\n```\n\nReplace `\u003CRELEASE>` with the installed release (e.g., `R2025b`). Display the link on its own line for readability:\n\n> View the MATLAB R2025b Release Notes by visiting this link:\n> https:\u002F\u002Fwww.mathworks.com\u002Fhelp\u002Fmatlab\u002Frelease-notes.html?startrelease=R2025b&endrelease=R2025b&rntext=&groupby=release&sortby=descending&searchHighlight=\n\nDo not show this link if the user only installed toolboxes or support packages without MATLAB.\n\n\n## Common Errors\n\n- **`ErrorCode::IncompatibleProduct`** (\"Selected products are incompatible\"): The destination folder most likely contains an existing MATLAB installation. Inform the user and ask them to choose an empty destination folder.\n\n## Key Functions and Patterns\n\n| Command \u002F Pattern | Purpose |\n|---|---|\n| `mpm install --inputfile=\u003Cfile>` | Install products defined in an input file |\n| `mpm_input_\u003Crelease>.txt` | Release-specific input file template from mathworks.com |\n| `product.\u003CName>` | Input file entry format for products and support packages |\n| `destinationFolder=\u003Cpath>` | Input file directive setting the install location |\n| `Start-Process -Verb RunAs -Wait` | Elevated execution on Windows (UAC) |\n| `Invoke-WebRequest -OutFile` | Download files in PowerShell |\n| `curl -fL -o` | Download files on Linux\u002FmacOS |\n\n## Notes\n- mpm installs required dependencies automatically.\n- Licensing and activation are separate workflows. Do not ask the user about licensing or activation at the end of the install.\n- Always use a release input file from:\n  https:\u002F\u002Fwww.mathworks.com\u002Fproducts\u002Fmpm.html\n\n----\n\nCopyright 2026 The MathWorks, Inc.\n\n----\n\n","# Installing MATLAB Products with MATLAB Package Manager (mpm) - Deterministic Protocol\n\nUse this skill when asked to install MathWorks products using MATLAB Package Manager (mpm) from the OS command line.\n\n$ARGUMENTS\n\n## When to Use\n\n- User asks to install MATLAB, Simulink, toolboxes, or support packages via the command line\n- User wants a scripted, repeatable MATLAB installation (CI\u002FCD, containers, fleet provisioning)\n- User asks about mpm, MATLAB Package Manager, or non-interactive MATLAB installs\n- User needs to add products to an existing MATLAB installation using mpm\n\n## When NOT to Use\n\n- User wants to install via the graphical MATLAB installer or MathWorks website\n- User is asking about MATLAB licensing or activation (separate workflow)\n- User wants to manage MATLAB Add-Ons from within MATLAB (use the Add-On Manager)\n- User needs to install MATLAB Engine API for Python, Java, or C++ (different process)\n\n## Non-Negotiable Determinism Contract (follow exactly)\n- Follow the steps in **Protocol** in order. Do not add extra steps or checks.\n- Use **only** the canonical shell for the OS. Do not switch shells.\n- Use **absolute paths** to `mpm` \u002F `mpm.exe`. Never rely on relative paths.\n- Retry downloads at most **once**. Otherwise stop and report the error.\n- If security software blocks execution: **stop** and instruct escalation. Do not bypass.\n\n## Safety Gate (Windows) — MANDATORY, NO EXCEPTIONS\n\n**STOP. Read this entire section before executing ANY Windows step.**\n\n1. **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.\n2. **NEVER** use bash heredoc syntax (`cat > file \u003C\u003C'EOF'`) or bash redirection (`echo ... >`) to create PowerShell scripts.\n3. **ALWAYS** write `.ps1` files using the **Write file tool**, then invoke with:\n   `powershell.exe -NoLogo -NoProfile -NonInteractive -ExecutionPolicy Bypass -File \u003Cabsolute-script-path>`\n4. Do not emit CMD-only syntax (`if not exist`, `set VAR=`, `%USERPROFILE%`). Use PowerShell equivalents (`Test-Path`, `$env:USERPROFILE`).\n\n5. **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.\n\n**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.**\n\nWindows script authoring pattern:\n- **WRONG**: `powershell.exe -Command \"$script = @'...`  (bash corrupts `$` and heredocs)\n- **WRONG**: `cat > C:\u002FWindows\u002FTemp\u002Fscript.ps1 \u003C\u003C'PS1' ... PS1`  (bash heredoc, breaks on Windows)\n- **CORRECT**: create a unique temp folder, use the **Write file tool** to write `.ps1` files into it, then run with `-File`\n\nUnique temp folder:\n- Before Step 1, create a timestamped working folder using the Bash tool:\n  - Windows: `mkdir -p \"C:\u002FUsers\u002F\u003Cusername>\u002FAppData\u002FLocal\u002FTemp\u002Fmpm-\u003CYYYYMMDD-HHMMSS>\"`\n  - Linux\u002FmacOS: `mkdir -p \"\u002Ftmp\u002Fmpm-\u003CYYYYMMDD-HHMMSS>\"`\n- Use this folder for ALL generated scripts and input files throughout the protocol\n- Because the folder is new, the Write file tool can always create files in it without needing to delete anything first\n- Delete the entire folder during the final cleanup step\n\nWindows PowerShell syntax reminders:\n- Bad: `if not exist C:\\Users\\name\\Downloads mkdir C:\\Users\\name\\Downloads` (CMD syntax)\n- Good: `if (-not (Test-Path -LiteralPath 'C:\\Users\\name\\Downloads')) { New-Item -ItemType Directory -Path 'C:\\Users\\name\\Downloads' | Out-Null }`\n\nDo not ask the user for the exact product name or identifier. Look it up using the appropriate mpm input file from https:\u002F\u002Fwww.mathworks.com\u002Fproducts\u002Fmpm.html\nDo not ask the user whether to install dependencies or not. mpm will take care of it. Just install whatever the user asked for, and let mpm do the rest.\nIf a user types the shortname of MATLAB releases, automatically use the correct expanded full name. e.g. 25a is R2025a, 25b is R2025b\n\n## Required Inputs (ask only if missing)\n1. Operating system (Windows, Linux, macOS)\n2. MATLAB release (for example `R2025b`)\n3. Installation destination (absolute path)\n4. Requested products \u002F toolboxes \u002F support packages\n\n## Confirmation Rule\nBefore executing any steps, always confirm the user's choices:\n- Release\n- Destination folder\n- Products\n- Support packages\n\nAsk for confirmation in one message. The user can reply `yes to all` to confirm everything at once. If they reply with specific changes, update the selections and confirm again.\nDisplay each value to be confirmed in its own new line.\nNote at the bottom of the confirmation message: \"Required dependencies will be installed automatically by mpm.\"\n\n## Plan Display (after confirmation, before execution)\n\nOnce the user confirms their inputs, display a clear installation plan before running any commands. Adapt the template below for the target OS (use forward slashes and `\u002Ftmp\u002F` for Linux\u002FmacOS, omit `.ps1` script references, and omit the UAC note). Use this format:\n\n```\nHere's what I'll do:\n\nWorking folder: \u003CC:\\Users\\\u003Cusername>\\AppData\\Local\\Temp\\mpm-YYYYMMDD-HHMMSS>\n\nStep 1 — Download mpm\n  Check for mpm at \u003Ccanonical mpm path>\n  Download from \u003CURL> if not present\n  Script: \u003Cworking folder>\\mpm_download.ps1\n\nStep 2 — Prepare input file\n  Download release template for \u003Crelease> from mathworks.com\n  Set destination folder: \u003Cdestination>\n  Enable products: \u003Ccomma-separated list>\n  Input file: \u003Cworking folder>\\mpm_input_\u003Creleaselower>.txt\n  Script: \u003Cworking folder>\\mpm_prepare_input.ps1\n\nStep 3 — Run installation\n  Execute mpm install using the prepared input file\n  \u003CWindows only: note that elevated permissions (UAC prompt) will be required>\n\nStep 4 — Verify\n  Confirm MATLAB binary exists: \u003Ccompletion artifact path>\n  Verify products via: \u003CDESTINATION>\u002Fappdata\u002Fprodcontents.json\n  \u003Cif support packages requested> Verify support packages via: \u003CSUPPORTPKGROOT>\u002Fappdata\u002Fprodcontents.json\n  Delete working folder: \u003Cworking folder>\n  \u003Cif MATLAB included> Show release notes: https:\u002F\u002Fwww.mathworks.com\u002Fhelp\u002Fmatlab\u002Frelease-notes.html?startrelease=\u003CRELEASE>&endrelease=\u003CRELEASE>\n```\n\nResolve all environment variables and shell-specific paths to absolute paths before displaying. Generate the timestamp for the working folder name at plan display time so it is fixed for the entire session.\nDo not start Step 1 until the user acknowledges the plan (a simple \"ok\", \"go\", \"yes\", or similar is enough).\n\nOfficial documentation:\n- Get mpm: https:\u002F\u002Fwww.mathworks.com\u002Fhelp\u002Finstall\u002Fug\u002Fget-mpm-os-command-line.html\n- mpm install: https:\u002F\u002Fwww.mathworks.com\u002Fhelp\u002Finstall\u002Fug\u002Fmpminstall.html\n\n## Execution Style\n\n> **Important:** When executing steps, do not narrate or explain what you are about to do. Just run the commands and report results concisely (success, failure, or error). Reserve commentary for confirmations, the plan display, and error reporting only.\n\n## Canonical Shell (used throughout the Protocol)\n- **Windows**: Windows PowerShell (`powershell.exe`)\n- **Linux**: `bash` \u002F `sh`\n- **macOS**: `zsh` or `bash` (Apple silicon only; Intel Mac is not supported — stop and inform the user)\n\n## Pre-Execution Checklist (verify before EVERY Windows step)\n\nBefore running any command in Steps 1–3 on Windows, confirm:\n- [ ] The PowerShell script was written using the **Write file tool** (not `-Command`, not heredoc, not `echo`)\n- [ ] The script is invoked with `powershell.exe ... -File \u003Cpath>` (not `-Command`)\n- [ ] No PowerShell code appears inline in any `bash` command\n\nIf any check fails, STOP and rewrite using the Write file tool.\n\n## Protocol (exactly 4 steps)\n\n### Step 1 - Ensure mpm exists at canonical path\n\nCanonical locations (resolve to absolute paths before use):\n- Windows: `\u003Cuser home>\\Downloads\\mpm.exe`\n- Linux: `\u003Cuser home>\u002FDownloads\u002Fmpm`\n- macOS: `\u003Cuser home>\u002FDownloads\u002Fmpm`\n\nIf the file exists at that path, reuse it. Otherwise download from:\n- Windows: https:\u002F\u002Fwww.mathworks.com\u002Fmpm\u002Fwin64\u002Fmpm\n- Linux: https:\u002F\u002Fwww.mathworks.com\u002Fmpm\u002Fglnxa64\u002Fmpm\n- macOS: https:\u002F\u002Fwww.mathworks.com\u002Fmpm\u002Fmaca64\u002Fmpm\n\n#### Windows (PowerShell)\n\n**MANDATORY: Use the Write file tool to create this script. NEVER use -Command or heredoc.**\n\n1. Create the working folder with the Bash tool (use the timestamp fixed at plan display time):\n\n```bash\nmkdir -p \"C:\u002FUsers\u002F\u003Cusername>\u002FAppData\u002FLocal\u002FTemp\u002Fmpm-YYYYMMDD-HHMMSS\"\n```\n\n2. Use the **Write file tool** to write the following content to `\u003Cworking folder>\\mpm_download.ps1`:\n\n```powershell\nparam(\n  [Parameter(Mandatory = $true)]\n  [string]$Destination\n)\nif (Test-Path -LiteralPath $Destination) {\n  Write-Host \"mpm already present at $Destination\"\n} else {\n  Write-Host \"Downloading mpm from https:\u002F\u002Fwww.mathworks.com\u002Fmpm\u002Fwin64\u002Fmpm - this may take a few minutes...\"\n  Invoke-WebRequest -Uri \"https:\u002F\u002Fwww.mathworks.com\u002Fmpm\u002Fwin64\u002Fmpm\" -OutFile $Destination -UseBasicParsing\n  if (-not (Test-Path -LiteralPath $Destination)) { throw \"mpm download failed: $Destination\" }\n  Write-Host \"mpm downloaded to $Destination\"\n}\n```\n\n3. Run it:\n\n```bash\npowershell.exe -NoLogo -NoProfile -NonInteractive -ExecutionPolicy Bypass -File \"\u003Cworking folder>\\mpm_download.ps1\" -Destination \"C:\\Users\\\u003Cusername>\\Downloads\\mpm.exe\"\n```\n\n#### Linux\u002FmacOS\n\nSee `reference\u002Flinux-macos-steps.md` for full shell scripts. Summary: create working folder at `\u002Ftmp\u002Fmpm-YYYYMMDD-HHMMSS`, download mpm with `curl -fL -o` to `~\u002FDownloads\u002Fmpm`, and `chmod +x`.\n\n### Step 2 - Download and edit the release input file\n\nAlways use a release template input file from:\nhttps:\u002F\u002Fwww.mathworks.com\u002Fproducts\u002Fmpm.html\n\nDownload the template input file for the requested release, then edit it:\n- Uncomment and set `destinationFolder` to the requested installation path.\n- Uncomment each `product.\u003CName>` line for requested products and support packages.\n- Add `noJRE=true` to the input file (on its own line, after `destinationFolder`). This prevents mpm from bundling a Java Runtime. Only omit this line if the user explicitly requests JRE installation.\n- Leave `updateLevel` commented unless the user requests a specific update.\n- Do not edit the checksum line (`?checksum=...`).\n\nAfter editing the file, verify:\n- The input file exists at the expected path.\n- `destinationFolder` matches the user-requested install path exactly.\n- Each requested `product.\u003CName>` line is uncommented (no leading `#`).\n- Non-requested products remain commented out.\n\nIf any verification fails, stop and retry the download once, then re-edit and re-verify.\nIf it still fails, stop and report the error.\n\nThe input file format uses `product.\u003CName>` entries for both products and support packages.\nYou must look up the exact `product.\u003CName>` identifiers in the release input file.\nProduct identifiers use underscores for spaces (e.g. \"Signal Processing Toolbox\" -> `product.Signal_Processing_Toolbox`).\n\n- Always display the full path to the ps1 script that was generated\n\n#### Windows (PowerShell)\n\n**MANDATORY: Use the Write file tool to create this script. NEVER use -Command or heredoc.**\n\n1. Use the **Write file tool** to write the following content to `\u003Cworking folder>\\mpm_prepare_input.ps1`:\n\n```powershell\nparam(\n  [Parameter(Mandatory = $true)]\n  [string]$Release,\n  [Parameter(Mandatory = $true)]\n  [string]$Destination,\n  [Parameter(Mandatory = $true)]\n  [string]$WorkingFolder,\n  [Parameter(Mandatory = $true)]\n  [string]$Products\n)\n\nSet-StrictMode -Version Latest\n$ErrorActionPreference = \"Stop\"\n\n# -File mode passes \"a,b\" as one string; split into an array\n$ProductList = $Products -split ',' | ForEach-Object { $_.Trim() }\n\n$releaseLower = $Release.ToLower()\n$inputUrl  = \"https:\u002F\u002Fwww.mathworks.com\u002Fcontent\u002Fdam\u002Fmathworks\u002Fmathworks-dot-com\u002Fproducts\u002Fmpm\u002Fmpm-input-${releaseLower}.txt\"\n$inputFile = Join-Path $WorkingFolder \"mpm_input_${releaseLower}.txt\"\n\nWrite-Host \"Downloading input file from $inputUrl...\"\nInvoke-WebRequest -Uri $inputUrl -OutFile $inputFile -UseBasicParsing\nif (-not (Test-Path -LiteralPath $inputFile)) {\n  throw \"Input file was not downloaded: $inputFile\"\n}\n\n$lines = Get-Content -LiteralPath $inputFile\n\n$lines = $lines | ForEach-Object {\n  if ($_ -match '^\\s*#?\\s*destinationFolder=') {\n    \"destinationFolder=$Destination\"\n    \"noJRE=true\"\n  }\n  else {\n    $_\n  }\n}\n\nforeach ($product in $ProductList) {\n  $escaped = [Regex]::Escape($product)\n  $lines = $lines | ForEach-Object {\n    if ($_ -match \"^\\s*#\\s*$escaped\\s*$\") {\n      $product\n    }\n    else {\n      $_\n    }\n  }\n}\n\nSet-Content -LiteralPath $inputFile -Value $lines -Encoding UTF8\n\n$lines = Get-Content -LiteralPath $inputFile\n\n$destinationLine = $lines | Where-Object { $_ -match '^destinationFolder=' } | Select-Object -First 1\nif (-not $destinationLine) { throw \"destinationFolder line not found in $inputFile\" }\nif ($destinationLine -ne \"destinationFolder=$Destination\") { throw \"destinationFolder mismatch: $destinationLine\" }\n\n$uncommentedProducts = $lines | Where-Object { $_ -match '^\\s*product\\.' }\n$unexpectedProducts  = $uncommentedProducts | Where-Object { $ProductList -notcontains $_ }\nif ($unexpectedProducts) { throw \"Unrequested products enabled: $($unexpectedProducts -join ', ')\" }\n\nforeach ($product in $ProductList) {\n  if (-not ($lines -contains $product)) { throw \"Requested product not enabled: $product\" }\n}\n\nWrite-Host \"Input file ready: $inputFile\"\n```\n\nNote: the script writes the input file to `\u003Cworking folder>\\mpm_input_\u003Creleaselower>.txt`, so cleanup of the working folder deletes it automatically. The input file path will be reported by the script on completion.\n\n2. Run it (substitute actual working folder, release, destination, and product identifiers):\n\n```bash\npowershell.exe -NoLogo -NoProfile -NonInteractive -ExecutionPolicy Bypass -File \"\u003Cworking folder>\\mpm_prepare_input.ps1\" -Release \"R2025b\" -Destination \"C:\\MATLAB\\R2025b\" -WorkingFolder \"\u003Cworking folder>\" -Products \"product.MATLAB,product.Simulink\"\n```\n\n#### Linux\u002FmacOS\n\nSee `reference\u002Flinux-macos-steps.md` for the full shell script. Summary: download the release input file with `curl`, edit with `sed` to set `destinationFolder` and uncomment requested products, then verify all edits.\n\n- Do not delete generated files yet; cleanup happens after Step 3.\n\n### Step 3 - Run the install command and completion check\n\n**IMPORTANT:**\n- When using `--inputfile`, do not pass any other mpm options.\n- Windows requires elevation. Use `Start-Process -Verb RunAs` for elevated execution.\n- Always display the fully expanded command before running it.\n- Substitute actual values for release, working folder, and destination in the snippets below.\n\n#### Windows\n\n**MANDATORY: Use the Write file tool to create a .ps1 script for this step. NEVER use -Command or heredoc. Then invoke with `powershell.exe ... -File \u003Cpath>`.**\n\nWrite the following to `\u003Cworking folder>\\mpm_install.ps1` using the **Write file tool**, then run with `-File`:\n\n```powershell\nparam(\n  [Parameter(Mandatory = $true)]\n  [string]$MpmPath,\n  [Parameter(Mandatory = $true)]\n  [string]$InputFile\n)\n\n$installArgs = @(\n  \"install\",\n  \"--inputfile=$InputFile\"\n)\n\n$display = '\"' + $MpmPath + '\" install ' + ('--inputfile=\"' + $InputFile + '\"')\nWrite-Host \"Running: $display\"\n\nStart-Process -FilePath $MpmPath -ArgumentList $installArgs -Verb RunAs -Wait\n```\n\nRun it:\n\n```bash\npowershell.exe -NoLogo -NoProfile -NonInteractive -ExecutionPolicy Bypass -File \"\u003Cworking folder>\\mpm_install.ps1\" -MpmPath \"C:\\Users\\\u003Cusername>\\Downloads\\mpm.exe\" -InputFile \"\u003Cworking folder>\\mpm_input_\u003Creleaselower>.txt\"\n```\n\n#### Linux\u002FmacOS\n\nSee `reference\u002Flinux-macos-steps.md`. Summary: run `mpm install --inputfile=\u003Cpath>` directly (no elevation needed).\n\n### Step 4 - Verification\n\nThis step defines **completion**. It is mandatory.\nWait until the mpm process has exited. Do not proceed until it is done.\nIf the completion artifact does not exist, stop and report failure. **Do not re-run Step 3.**\n\nCompletion artifacts (use the destination folder you set in the input file):\n- **Windows**: `\u003CDESTINATION>\\bin\\matlab.exe`\n- **Linux**: `\u003CDESTINATION>\u002Fbin\u002Fmatlab`\n- **macOS**: `\u003CDESTINATION>\u002FContents\u002FMacOS\u002FMATLAB`\n\nUse the Bash tool with `test -f` to check existence. Do **not** use `powershell.exe -Command` for this check.\n\n```bash\ntest -f \"\u003CDESTINATION>\u002Fbin\u002Fmatlab.exe\" && echo \"VERIFIED\" || echo \"NOT FOUND\"\n```\n\n#### Per-item verification\n\nAfter confirming the MATLAB binary exists, verify each requested item was installed. Products and support packages are stored in **separate locations** with separate `prodcontents.json` files. Do not check one location for items that belong in the other.\n\n**Products** (items whose mpm identifier does NOT contain `Support_Package`):\n- Read `\u003CDESTINATION>\u002Fappdata\u002Fprodcontents.json` using the Read tool.\n- This is a JSON object. Keys are product names with version and platform tokens (e.g. `\"Simulink 25.1 win64\"`).\n- For each requested product, check that a key exists whose name starts with the product's display name (strip the `product.` prefix and replace underscores with spaces). For example, `product.Signal_Processing_Toolbox` matches a key starting with `Signal Processing Toolbox`.\n\n**Support packages** (items whose mpm identifier contains `Support_Package`):\n- Derive the support package root based on platform:\n  - **Windows:** `C:\\ProgramData\\MATLAB\\SupportPackages\\\u003CRELEASE>`\n  - **Linux:** `\u002Fusr\u002Flocal\u002FMATLAB\u002FSupportPackages\u002F\u003CRELEASE>`\n  - **macOS:** `~\u002FLibrary\u002FApplication Support\u002FMathWorks\u002FMATLAB\u002FSupportPackages\u002F\u003CRELEASE>`\n- Read `\u003CSUPPORTPKGROOT>\u002Fappdata\u002Fprodcontents.json` using the Read tool.\n- If the file does not exist, the support package installation failed. Report failure.\n- For each requested support package, check that a matching key exists (same name mapping as products above).\n\nReport **Verified** or **Not found** for each item. If any item is not found, stop and report which items failed.\n\nAfter all items are verified, delete the entire working folder and its contents using the Bash tool:\n\n```bash\nrm -rf \"C:\u002FUsers\u002F\u003Cusername>\u002FAppData\u002FLocal\u002FTemp\u002Fmpm-YYYYMMDD-HHMMSS\"\n```\n\n#### Release Notes Link\n\nOnly if MATLAB (the base product) was included in the installation, provide a link to the release notes after successful verification and cleanup:\n\n```\nhttps:\u002F\u002Fwww.mathworks.com\u002Fhelp\u002Fmatlab\u002Frelease-notes.html?startrelease=\u003CRELEASE>&endrelease=\u003CRELEASE>&rntext=&groupby=release&sortby=descending&searchHighlight=\n```\n\nReplace `\u003CRELEASE>` with the installed release (e.g., `R2025b`). Display the link on its own line for readability:\n\n> View the MATLAB R2025b Release Notes by visiting this link:\n> https:\u002F\u002Fwww.mathworks.com\u002Fhelp\u002Fmatlab\u002Frelease-notes.html?startrelease=R2025b&endrelease=R2025b&rntext=&groupby=release&sortby=descending&searchHighlight=\n\nDo not show this link if the user only installed toolboxes or support packages without MATLAB.\n\n\n## Common Errors\n\n- **`ErrorCode::IncompatibleProduct`** (\"Selected products are incompatible\"): The destination folder most likely contains an existing MATLAB installation. Inform the user and ask them to choose an empty destination folder.\n\n## Key Functions and Patterns\n\n| Command \u002F Pattern | Purpose |\n|---|---|\n| `mpm install --inputfile=\u003Cfile>` | Install products defined in an input file |\n| `mpm_input_\u003Crelease>.txt` | Release-specific input file template from mathworks.com |\n| `product.\u003CName>` | Input file entry format for products and support packages |\n| `destinationFolder=\u003Cpath>` | Input file directive setting the install location |\n| `Start-Process -Verb RunAs -Wait` | Elevated execution on Windows (UAC) |\n| `Invoke-WebRequest -OutFile` | Download files in PowerShell |\n| `curl -fL -o` | Download files on Linux\u002FmacOS |\n\n## Notes\n- mpm installs required dependencies automatically.\n- Licensing and activation are separate workflows. Do not ask the user about licensing or activation at the end of the install.\n- Always use a release input file from:\n  https:\u002F\u002Fwww.mathworks.com\u002Fproducts\u002Fmpm.html\n\n----\n\nCopyright 2026 The MathWorks, Inc.\n\n----\n\n",{"name":5,"license":25,"metadata":26,"description":7},"MathWorks BSD-3-Clause",{"author":27,"version":28},"MathWorks","1.3","master","49e49abf2f670d429e0b7e2c0349739c3fdd5cbe","skills\u002Fmatlab-install-products",5,"https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium","https:\u002F\u002Fgithub.com\u002Fstanfish06","https:\u002F\u002Fwww.stanfish.dev\u002F","2026-11-14 21:31:37",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add stanfish06\u002Fskillquarium --skill matlab-install-products",{"tool":43,"command":44},"bunx","bunx skills add stanfish06\u002Fskillquarium --skill matlab-install-products",{"tool":46,"command":47},"pnpm","pnpm dlx skills add stanfish06\u002Fskillquarium --skill matlab-install-products","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fmatlab-install-products\u002FSKILL.md",true,[51,56,62],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":16},"LICENSE.md","LICENSE","许可证",1482,{"path":57,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":60,"sourceHtmlUrl":61},"manifest.yaml","REFERENCE","参考文档",347,"https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fmatlab-install-products\u002Fmanifest.yaml",{"path":63,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":64,"sourceHtmlUrl":65},"reference\u002Flinux-macos-steps.md",2845,"https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fmatlab-install-products\u002Freference\u002Flinux-macos-steps.md",[67,75,84,91,98,105],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":71,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":20},"01M76ZJTRVA456GD7K8Y3EP82H","zarr-python","Stores and queries chunked N-D scientific arrays with Zarr-Python 3, including codecs, sharding, S3\u002FGCS storage, and NumPy\u002FDask\u002FXarray integration. Use for array layout, bounded I\u002FO, format migration, or scientific metadata preservation.","MIT","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fzarr-python\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":79,"licenseFileUrl":80,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":20},"01M76ZJQZ15Q1HKC5V85NHE325","yeet","Publish local changes to GitHub by confirming scope, committing intentionally, pushing the branch, and opening a draft PR through the GitHub app from this plugin, with `gh` used only as a fallback where connector coverage is insufficient.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":79,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":20},"01M76ZJ8ASZ4QYQ70Y6SBA4Z4S","xarray","N-dimensional labeled arrays and datasets in Python. Built on top of NumPy and Dask. It introduces labels in the form of dimensions, coordinates, and attributes on top of raw NumPy-like arrays, making data analysis in physical sciences more intuitive and less error-prone. Use for working with multi-dimensional scientific data, NetCDF\u002FGRIB\u002FZarr files, climate\u002Fweather\u002Foceanographic datasets, remote sensing, geospatial imaging, large out-of-memory datasets with Dask, and labeled array operations.","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fxarray\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":71,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":20},"01M76ZHFBXD6VXPQ02VCEG202B","writing-mstest-tests","Use when asked to fix, rewrite, update, improve, modernize, show corrected code for, or explain existing MSTest tests or MSTest-specific configuration. Use for \"review\" when corrected code or edits are wanted, even for one pasted assertion or passing tests with bad failure output. Covers expected\u002Factual labels; generic Boolean, collection, string, numeric, null, identity, exception, hard-cast, and object[] checks; TestContext\u002Flifecycle; timeout\u002Fcancellation; OS\u002FCI conditions, retry, cleanup, parallelization, MSTest.Sdk project setup, and MSTESTxxxx. Honor the installed MSTest version. DO NOT USE to design new test cases (code-testing), perform report-only audits, create project files rather than explain MSTest setup, run tests, migrate frameworks, or handle non-MSTest\u002Fnon-.NET code.","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fwriting-mstest-tests\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":71,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":20},"01M76ZDFDF4N88RH6HSYGS7GP2","wgs-prs","End-to-end WGS to polygenic risk score pipeline. Takes paired-end FASTQ files (or a pre-existing VCF) through nf-core\u002Fsarek for variant calling, applies VCF QC (normalisation, hard filtering, Ti\u002FTv and Het\u002FHom checks), then computes polygenic risk scores via the PGS Catalog. Fills the FASTQ to VCF gap upstream of the gwas-prs skill.","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fwgs-prs\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":79,"licenseFileUrl":109,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":20},"01M76ZCC1SC68J42QK4MDC8RCG","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[],[]]