Skip to content

matlab/matlab-agentic-toolkit / skills-catalog/matlab-core/matlab-install-products

matlab-install-products

Verified

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.

FileKindSize
SKILL.mdskill md23.2 KB
manifest.yamlconfig396 B
reference/linux-macos-steps.mdmarkdown3.8 KB

reference/linux-macos-steps.md

View on GitHub
# Linux/macOS Steps for mpm Installation

## Step 1 - Download mpm

Create the working folder with `mkdir -p /tmp/mpm-YYYYMMDD-HHMMSS`, then print a progress message (`echo "Downloading mpm - this may take a few minutes..."`), use `curl -fL -o` to download mpm to `<user home>/Downloads/mpm`, and `chmod +x` to make it executable.

```sh
set -eu
working_folder="/tmp/mpm-YYYYMMDD-HHMMSS"
mkdir -p "$working_folder"
mpm_path="$HOME/Downloads/mpm"

if [ -f "$mpm_path" ]; then
  echo "mpm already present at $mpm_path"
else
  echo "Downloading mpm - this may take a few minutes..."
  curl -fL -o "$mpm_path" "https://www.mathworks.com/mpm/glnxa64/mpm"  # Linux
  # macOS: curl -fL -o "$mpm_path" "https://www.mathworks.com/mpm/maca64/mpm"
  chmod +x "$mpm_path"
  echo "mpm downloaded to $mpm_path"
fi
```

## Step 2 - Download and edit the release input file

```sh
set -eu
release="R2025b"
working_folder="/tmp/mpm-YYYYMMDD-HHMMSS"
input_url="https://www.mathworks.com/content/dam/mathworks/mathworks-dot-com/products/mpm/mpm-input-${release,,}.txt"
input_file="${working_folder}/mpm_input_${release,,}.txt"

curl -fL -o "$input_file" "$input_url"

if [ ! -f "$input_file" ]; then
  echo "Input file was not downloaded: $input_file" >&2
  exit 1
fi

expected_destination="/usr/local/MATLAB/R2025b"
requested_products="product.MATLAB product.Simulink"

# Edit: set destinationFolder and add noJRE=true
sed -i'' "s|^#*\s*destinationFolder=.*|destinationFolder=$expected_destination|" "$input_file"
sed -i'' "/^destinationFolder=/a noJRE=true" "$input_file"

# Edit: add caller=agent after noJRE=true
sed -i'' "/^noJRE=true/a caller=agent" "$input_file"

# Edit: uncomment requested products
for product in $requested_products; do
  sed -i'' "s|^#\s*\(${product}\)\s*$|\1|" "$input_file"
done

# Verify: destinationFolder
destination_line=$(grep -E '^destinationFolder=' "$input_file" | tr -d '\r')
if [ "$destination_line" != "destinationFolder=$expected_destination" ]; then
  echo "destinationFolder mismatch: $destination_line" >&2
  exit 1
fi

# Verify: caller=agent line present
grep -qx 'caller=agent' "$input_file" || { echo "caller=agent line not found in $input_file" >&2; exit 1; }

# Verify: no unrequested products uncommented
uncommented_products=$(grep -E '^[[:space:]]*product\.' "$input_file" | tr -d '\r')
for line in $uncommented_products; do
  case " $requested_products " in
    *" $line "*) ;;
    *) echo "Unrequested product enabled: $line" >&2; exit 1 ;;
  esac
done

# Verify: all requested products are uncommented
for product in $requested_products; do
  grep -qx "$product" "$input_file" || { echo "Requested product not enabled: $product" >&2; exit 1; }
done
```

## Step 3 - Run the install command

When using `--inputfile`, pass no other mpm options — mpm rejects `--inputfile` combined with any other option. The caller value travels in the input file as the `caller=agent` line added in Step 2, not on the command line.

The `caller=agent` line uses the fixed value `agent` — it records only that an automation agent performed the install, not which one, so do not substitute an agent name or model. mpm records the value in its usage data (uppercased), so casing is not significant. The `caller=agent` line is a usage-data tag, not an installation setting, so it does not need to appear in the confirmation, plan, progress messages, or summary. If the user asks about it, explain that it marks the install as agent-initiated in mpm usage data and has no effect on what gets installed or where.

```sh
set -eu
MPM="$HOME/Downloads/mpm"
input_file="/tmp/mpm-YYYYMMDD-HHMMSS/mpm_input_r2025b.txt"

echo "Running: $MPM install --inputfile=\"$input_file\""
"$MPM" install --inputfile="$input_file"
```

Completion artifact: `<DESTINATION>/bin/matlab` (Linux) or `<DESTINATION>/Contents/MacOS/MATLAB` (macOS).

----

Copyright 2026 The MathWorks, Inc.

----

writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 197kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall