Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →matlab/create-sdi-run
Import data into the Simulation Data Inspector (SDI) from MAT, CSV, or Excel files, from workspace variables, or from a Simulink simulation.
Passed 21 of 21 test cases with the skill, and 11 of 21 without it.
and 9 more in the full report
10 fixed12 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
I have a MAT-file at `logs/flight_data.mat` containing logged signals. Provide a MATLAB command to import this file directly into the Simulation Data Inspector in a single step without manually calling load on workspace variables first.
| Checked | Without skill | With skill |
|---|---|---|
| The response uses Simulink.sdi.createRun with the 'file' source argument. | Missed | Passed |
The instructions your model reads when the skill loads.
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.
.mat, .csv, or .xlsx file of logged data and wants to view it in SDI.sim(model) and wants to see the logged signals.timeseries, timetable, or Simulink.SimulationData.Dataset variables in the workspace and wants an SDI run.Simulink.sdi.createRun, Simulink.sdi.getAllRunIDs, or Simulink.sdi.getRun.Simulink.sdi.compareRuns).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..mf4), ULG, ROS bag, CAN log, or HDF5 formats — see references/format-support.md for what SDI reads natively vs. what needs a different toolbox..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.Answer these four questions in order. The first "yes" tells you what to do.
After sim(model) with signal logging enabled, SDI auto-populates one run. Do not call createRun — that produces a duplicate.
before = Simulink.sdi.getAllRunIDs;
simOut = sim("myModel");
after = Simulink.sdi.getAllRunIDs;
if numel(after) > numel(before)
Simulink.sdi.view; % done — just open the window
end
If no new run appeared, logging is off. Enable it via the Simulink Agentic Toolkit model_edit tool with a configure op setting DataLogging on the target port, then re-simulate — or fall back to Step 3 with simOut. As a last resort, ask the user to right-click a signal → Log Selected Signals in the Simulink editor themselves; that step is for the user to perform, not the agent.
test cases passed, vs 11 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.