Traction scoreGitHub stars can be faked, so popularity alone can be misleading. Traction Score looks for broader signs of recent attention, adoption, and active maintenance.
This toolkit provides a set of capabilities for embedded software engineers to manage the transition from Simulink models to deployable code. It streamlines the technical requirements for generating C and C++ code, ensuring that model elements are correctly represented in the final output.
The skills focus on precise control over code interface configurations and the authoring of Classic AUTOSAR Software Components, making the process of preparing models for embedded targets more structured and verifiable.
WHO IT'S FOR
Embedded software engineers
automate Simulink model configuration for code generation
Compatible AgentsThe repository documents support for these agents. The skills may also work with other agents that can load SKILL.md files, but they may need some setup or small changes.
Follow the documented setup, then try a first task.
I’m using
Automated setup through MATLAB Add-On Manager
Installs: Complete Simulink Agentic Toolkit installation and skill registration; the automated installer supports both the MATLAB and Simulink Agentic Toolkits. The listed skill paths are a bounded selection relevant to the starter tasks, not the bundle's complete inventory. · Claude Code, Copilot, Codex, Amp, Gemini CLI
Before you start
MATLAB R2023a or later with Simulink.
A supported AI coding agent.
Some skills require additional products; check each skill's manifest.yaml requires-products field.
Existing users of the previous agent-driven workflow must first uninstall that custom installation and global configuration following the repository's migration guide.
Download agenticToolkitInstaller.mltbx from the latest Simulink Agentic Toolkit release using the documented release link.
Open the downloaded agenticToolkitInstaller.mltbx file to install the installer add-on through MATLAB Add-On Manager.
After the add-on is installed, enter this command in MATLAB.
Automated setup with programmatic add-on installation
Installs: Complete Simulink Agentic Toolkit installation and skill registration; this is the documented automated fallback for systems where Add-On Manager fails. The installer supports both the MATLAB and Simulink Agentic Toolkits. The listed skill paths are a bounded selection relevant to the starter tasks, not the bundle's complete inventory. · Claude Code, Copilot, Codex, Amp, Gemini CLI
Before you start
MATLAB R2023a or later with Simulink.
A supported AI coding agent.
The downloaded agenticToolkitInstaller.mltbx file must be accessible to MATLAB under that filename when the installation command is entered.
Some skills require additional products; check each skill's manifest.yaml requires-products field.
Existing users of the previous agent-driven workflow must first uninstall that custom installation and global configuration following the repository's migration guide.
Download agenticToolkitInstaller.mltbx from the latest Simulink Agentic Toolkit release using the documented release link.
If Add-On Manager fails to launch, enter this command in MATLAB to install the downloaded agenticToolkitInstaller.mltbx file programmatically.
A search topic to replace <topic>, such as motor control, PID, or battery.
The owning MathWorks product must be installed only if you later choose to open a returned example.
Use the finding-simulink-examples skill to search the shipped MathWorks examples database for five examples about <topic>. Do not open anything. Return each match's name, open command verbatim, and a concise description.
An accessible Simulink model name to replace <model-name>.
A stop-time value to replace <stop-time>.
MATLAB R2023a or later with Simulink.
Use the simulating-simulink-models skill to run <model-name> non-destructively with StopTime set to <stop-time> through Simulink.SimulationInput. Report which output properties are available, including any logged signal names, without modifying the .slx file.
Conversation context or reproduction details showing what happened and what was expected.
Any exact error messages or relevant tool output.
Use the filing-bug-reports skill to create a standalone Markdown bug report for <defect>. Include the action and intent, actual behavior and exact errors, expected behavior, reproduction details, and available environment information. Do not prescribe a root cause or solution.
Claude
Codex
Gemini CLI
Copilot
Amp