Add, configure, and manage faults on Simulink, Simscape, and System Composer model signals for robustness analysis and safety validation.
SkillScore78Maintained
Automatic
◆Coding pack
Last verified 8/15/2026
What it changes
Passed 18 of 23 test cases with the skill, and 8 of 23 without it.
Without skill35%
With skill78%
Checks it passed that the model alone missed
Calls activate on the intended fault object
Saves fault metadata using Simulink.fault.save
Executes addBehavior before configuring trigger properties
and 12 more in the full report
10 fixed8 passed either way5 still failing0 broke
Pass-rate lift
+43 pp
Tokens
+59%
Agent turns
0%
Response time
-45%
Model gemini-3.6-flashMeasured 8/15/2026v118 of 23 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 10
Prompt
After creating and updating several faults on model 'PowerInverter', should I call `save_system('PowerInverter')` to save the fault definitions?
What was checked, without and with the skill
Checked
Without skill
With skill
Calls Simulink.fault.save to save fault metadata XML files
Missed
Passed
case-18 · gemini-3.6-flash · 8/15/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md116 lines7 files
Fault Injection
Use evaluate_matlab_code with the Simulink.fault API to programmatically inject faults into Simulink models. Faults override signal values at block ports to simulate hardware failures, sensor faults, and actuator malfunctions.
When to Use
Injecting sensor stuck-at faults, noise, or bias for safety analysis (Simulink, Simscape, System Composer)
Validating FMEA failure modes through simulation
Testing controller robustness against actuator or sensor failures
Adding fault placeholders (without behavior) for FMEA traceability before defining fault logic
Exporting models with embedded fault behavior for teams without Simulink Fault Analyzer
Registering custom fault behavior libraries
Synchronizing (also called resync / sync / synchronize faults / update fault references) fault information from referenced models, subsystems, or linked libraries into a parent model
When NOT to Use
Creating FMEA spreadsheets or safety analysis documents -> use manage-safety-analysis
Building or editing model structure -> use building-simulink-models
Running standard (non-faulted) simulations -> use simulating-simulink-models
Writing pass/fail tests -> use testing-simulink-models