SkillAgentSearch skills...

managing-simulink-projects

Manages MATLAB projects for Simulink workflows: path management, file registration, labels, source control configuration, and project lifecycle

Install / Use

npx skills add matlab/simulink-agentic-toolkit --skill managing-simulink-projects

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

83/100

Category

Automation

Supported Platforms

Universal

Our assessment of managing-simulink-projects

managing-simulink-projects scores 83/100 on our quality scale, 2222nd of 2,769 Automation skills we index.

Its SKILL.md is 5.1 KB long, split into 7 sections with 1 code example: a solid amount of guidance for an agent.

With 1,148 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
15/20
Description
15/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so managing-simulink-projects is actively maintained.
  • Our last check on 2026-10-15 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-04. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

managing-simulink-projects compared with similar skills

All 4 of these similar skills score higher than managing-simulink-projects; compare them before choosing.

SkillScoreStarsUpdatedFormat
managing-simulink-projects (this skill)by matlab831.1k2mo agoSKILL.md
Agent-Reachby Panniantong100112.7k9d agoCLAUDE.md
rufloby ruvnet10082.0ktodayCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10039.9k8d agoCLAUDE.md
Scraplingby D4Vinci100103.9ktodayMCP Server

Frequently asked questions

How do I install managing-simulink-projects?
Run npx skills add matlab/simulink-agentic-toolkit --skill managing-simulink-projects. The install tabs above show the steps for each supported agent.
Which AI agents does managing-simulink-projects work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is managing-simulink-projects safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is managing-simulink-projects still maintained?
The repository was last updated about 2 months ago, so managing-simulink-projects is actively maintained.

name: managing-simulink-projects 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. license: https://www.mathworks.com/content/dam/mathworks/license/pmrl/license.md metadata: author: MathWorks version: "1.1"

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.

  4. Single-project constraint. Only one project can be open at a time. Creating or opening a new project silently closes the current one (running its shutdown scripts). currentProject throws an error when no project is open — it does not return empty.

Guardrails

Always:

  • Use addPath(proj, folder) for every folder containing dictionaries, referenced models, requirements, or profiles
  • Pass filename only (not full paths) to addDataSource, set_param(...,'DataDictionary',...), and slreq.createLink
  • Use absolute paths for SimulinkCacheFolder and SimulinkCodeGenFolder: proj.SimulinkCacheFolder = fullfile(proj.RootFolder, 'work')
  • Call updateDependencies(proj) before querying proj.Dependencies
  • Close the current project before creating or opening another
  • Use .graphml extension for DependencyCacheFile
  • Use .gitignore for excluding derived files from source control
  • Add requirements folder to project path when linking requirements to models
  • Register .slmx link-store files with the project (guarded by isfile check)

Ask First:

  • Deleting files from a project (removeFile then disk delete)
  • Modifying startup/shutdown scripts (affects all users who open the project)
  • Changing project references (affects dependent projects)

Never:

  • Use proj.IgnoredFilePatterns — throws "Feature not supported" for all project types from createProject
  • Use cat.Labels — the correct property is cat.LabelDefinitions
  • Use 'string' as a label DataType — valid types are 'none', 'char', 'double', 'integer', 'logical'
  • Use findFile (singular) for label queries in R2024a+ — use findFiles (plural). ONLY use findFile with R2023a/b
  • Pass full file paths to filename-only APIs
  • Attempt to open two projects simultaneously
  • Use clear all in startup scripts — it wipes the proj variable

Task Routing

| Intent | Reference | |--------|-----------| | Add files/folders to project, manage project path | references/path-and-file-management.md | | Set up labels for automation pipelines | references/labels-and-automation.md | | Link data dictionaries to models | references/data-dictionaries.md | | Configure model references across folders | references/model-references.md | | Configure source control, cache folders, .gitignore | references/source-control-and-caching.md | | Configure startup/shutdown scripts | references/path-and-file-management.md (Startup and Shutdown Scripts section) | | Diagnose broken references or health check failures | Start with Verification below, then route to the relevant reference |

Verification

Run after every project modification:

results = runChecks(proj);
updateDependencies(proj);
deps = proj.Dependencies;  % digraph

If runChecks reports issues, inspect which folders are missing from the project path — this is the root cause of most failures.


Copyright 2026 The MathWorks, Inc.


Related Skills

View on GitHub
GitHub Stars1.1k
CategoryAutomation
Updated2mo ago
Forks106

Languages

HTML

Trust signals

88/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium