Agent skill · Data & Analytics

authoring-simulink-inputs

Synthesize new waveforms from scratch for Simulink inports using createInputDataset. Use ONLY when the user asks to generate, create, or synthesize signals (step, ramp, sine, chirp, pulse, noise) to populate a Dataset for External Inputs or Signal Editor. Covers timeseries and timetable formats with correct data type, interpolation, units, and dimensions. Also covers function-call and trigger inport timing setup. Do NOT use when the user wants to load, import, or read existing data from files (MAT, CSV, spreadsheet) — even if that data will be used as model input. Do NOT use for running simula

matlabgithub.com/matlabGitHub ↗
claude-codecodexcopilotNOASSERTION
Install
npx skills add matlab/simulink-agentic-toolkit --skill authoring-simulink-inputs --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 4
SKILL.md size: 9 KB
Bundled scripts: none
Version: 1.0
Declared author: MathWorks
Path: skills-catalog/simulink-simulation/authoring-simulink-inputs/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 903
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Author Input Signals Create populated input signal datasets for Simulink models using `createInputDataset` as the scaffold, then populating with meaningful waveforms while preserving all signal metadata. ## When to Use - User asks to **generate or create synthetic waveforms** (step, ramp, sine, chirp, pulse, noise, constant) for a model's inports - User wants to **populate a Dataset** created by `createInputDataset` with meaningful signal data - User needs signals for **Signal Editor** scenarios - User describes desired **input signal behavior** in natural language (e.g., "ramp from 0 to 10", "sine at 5 Hz") - User wants **timetable-based input signals** for inports - User needs to set up **function-call timing** or configure trigger/enable inport signals - User wants to replace **zero-filled scaffold** data with realistic waveforms ## When NOT to Use - User wants to **simulate** the model, **run** it, or **plot outputs** — use `simulating-simulink-models` instead. This skill only creates input data; it never runs `sim()` or produces plots. - User wants to **load, import, or read** data from existing files (CSV, MAT, spreadsheet, .mat workspace) — even if the destination is a mod

What's inside
Steps it walks through
  1. When to Use
  2. When NOT to Use
  3. Output
  4. Must-Follow Rules
  5. Workflow
  6. 1. Create the scaffold (inside a function)
  7. 2. Populate each element (inside the same function)
  8. Creating Multiple Datasets
  9. Bus Signal Inports
  10. Function-Call Inports
  11. Signal Types
  12. Interpolation and Continuity (explicit set — use only when overriding scaffold)
  13. Guardrails
Ships with 3 files
  • manifest.yaml
  • references/dataset-patterns.md
  • references/signal-patterns.md
More from simulink-agentic-toolkit
All skills →
About this skill
What does the authoring-simulink-inputs skill do?

Synthesize new waveforms from scratch for Simulink inports using createInputDataset. Use ONLY when the user asks to generate, create, or synthesize signals (step, ramp, sine, chirp, pulse, noise) to populate a Dataset for External Inputs or Signal Editor. Covers timeseries and timetable formats with correct data type, interpolation, units, and dimensions. Also covers function-call and trigger inport timing setup. Do NOT use when the user wants to load, import, or read existing data from files (MAT, CSV, spreadsheet) — even if that data will be used as model input. Do NOT use for running simula

How do I install it?

Run `npx skills add matlab/simulink-agentic-toolkit --skill authoring-simulink-inputs --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From matlab/simulink-agentic-toolkit, a repository with 903 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going