# Managing Simulink Projects

Manages MATLAB projects for Simulink workflows: path management, file registration...

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

## Install

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

## Description

Manages MATLAB projects for Simulink workflows: path management, file registration, labels, source control configuration, and project lifecycle. Use when creating projects, adding models/dictionaries/requirements to projects, configuring labels for automation, fixing broken model references, or setting up source control for Simulink artifacts.

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

# Managing Simulink Projects

MATLAB projects coordinate Simulink workflows, they manage the MATLAB path (which Simulink uses to resolve model references, data dictionaries, and requirements), track file membership for source control, and provide label-based automation for selecting targets in CI/CD pipelines.

## When to Use

- Creating a new MATLAB project for Simulink models
- Adding models, data dictionaries, or requirements to an existing project
- Configuring project paths so Simulink can resolve references
- Setting up labels for automation (test selection, code generation targets)
- Configuring source control and cache folders
- Diagnosing broken model references, missing dictionaries, or failing project health checks

## When NOT to Use

- Building or editing model structure (blocks, connections) → use `building-simulink-models`
- Writing or running tests → use `testing-simulink-models`
- Drafting requirements content → use `generate-requirement-drafts`
- Running simulations for analysis → use `simulating-simulink-models`

## Mental Model

Four principles that prevent the most common failures:

1. **Registration ≠ path.** `addFile` registers a file with the project for source control tracking. `addPath` puts a folder on the MATLAB path so Simulink can resolve artifacts by filename. These are independent operations, you almost always need both.

2. **Filename-only resolution.** Data dictionaries (`set_param(...,'DataDictionary',...)`, `addDataSource`), model references, and requirements all resolve via MATLAB path using **filename only**, never full paths. The containing folder must be on the project path.

3. **`addPath` is not recursive.** Each subfolder containing resolvable artifacts needs its own `addPath` call.

The rest: https://github.com/matlab/simulink-agentic-toolkit/blob/HEAD/skills-catalog/model-based-design-core/managing-simulink-projects/SKILL.md