# Create Sdi Run

Import data into the Simulation Data Inspector (SDI) from MAT, CSV, or Excel files...

- Repository: https://github.com/matlab/simulink-agentic-toolkit (1305 stars)
- Category: Documents
- License: see repository
- Last updated: 2026-10-29
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add matlab/simulink-agentic-toolkit --skill create-sdi-run -g -a claude-code -y`
Codex: `npx skills add matlab/simulink-agentic-toolkit --skill create-sdi-run -g -a codex -y`
Cursor: `npx skills add matlab/simulink-agentic-toolkit --skill create-sdi-run -g -a cursor -y`
Gemini CLI: `npx skills add matlab/simulink-agentic-toolkit --skill create-sdi-run -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add matlab/simulink-agentic-toolkit`

## Description

Import data into the Simulation Data Inspector (SDI) from MAT, CSV, or Excel files, from workspace variables, or from a Simulink simulation. Use when the user wants to view a logged file in SDI, load a bench-test log, or verify what a just-completed `Simulink.sdi.createRun` or `sim(model)` produced. Covers the `'file'`, `'vars'`, and `'namevalue'` sources of `createRun`, the auto-populate behavior after `sim()`, and post-import verification. Not for comparing existing runs (use `Simulink.sdi.compareRuns`); not for streaming data live during a running simulation (use `Simulink.sdi.createRunOrAddToStreamedRun`, a separate API); and not for authoring Gherkin or Simulink Test test cases, assertions, or regression tests (use `testing-simulink-models`). Do not activate on test-authoring or verification prompts even when no test-authoring skill is available, say so and stop.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Create SDI Run

Get data into the Simulation Data Inspector using the shortest path that works. Most agents reflexively read files into the workspace and rebuild signals by hand; this skill teaches the direct paths and when each applies.

## When to Use

- User has a `.mat`, `.csv`, or `.xlsx` file of logged data and wants to view it in SDI.
- User just ran `sim(model)` and wants to see the logged signals.
- User has `timeseries`, `timetable`, or `Simulink.SimulationData.Dataset` variables in the workspace and wants an SDI run.
- User asks about `Simulink.sdi.createRun`, `Simulink.sdi.getAllRunIDs`, or `Simulink.sdi.getRun`.

## When NOT to Use

- Comparing two existing runs, that is a distinct workflow (`Simulink.sdi.compareRuns`).
- **Streaming data live during a running simulation**, this is a separate API (`Simulink.sdi.createRunOrAddToStreamedRun`), not a mode of `createRun`. Prompts like "stream data into SDI while my sim is running" belong to that API. Do not activate on those.
- Files in MDF (`.mf4`), ULG, ROS bag, CAN log, or HDF5 formats, see [references/format-support.md](references/format-support.md) for what SDI reads natively vs. what needs a different toolbox.
- Customizing plot layout, cursors, or subplot arrangement beyond opening the SDI window.
- **Authoring Gherkin `.feature` files, Simulink Test cases, `matlab.unittest` classes, or any pass/fail assertions or regression tests** for a model or subsystem, use `testing-simulink-models` (Gherkin-based `model_test`, requires Simulink Test). Prompts like "write a Gherkin test for X", "verify abs(-5) equals 5", "create a regression test for this subsystem", or any request whose deliverable is a test artifact belong there. Do **not** activate this skill on such prompts even when `testing-simulink-models` is unavailable, in that case, tell the user which skill is missing and stop.

## Workflow

Answer these four questions **in order**. The first "yes" tells you what to do.

The rest: https://github.com/matlab/simulink-agentic-toolkit/blob/HEAD/skills-catalog/simulink-simulation/create-sdi-run/SKILL.md