Slci Compatibility Analysis
Use when you need to verify a Simulink model is compatible with SLCI code inspection...
Install
npx skills add matlab/simulink-agentic-toolkit --skill slci-compatibility-analysis -g -a claude-code -y- Repository
- matlab/simulink-agentic-toolkit1.3k
- Category
- Engineering
- Updated
- 6d ago
- License
- See repository
- Context cost
- Mediumabout 2,892 tokens
- Runs scripts
- No, instructions only
What it does
Use when you need to verify a Simulink model is compatible with SLCI code inspection, or to apply fixes for identified incompatibilities. Checks model configuration, identifies incompatibilities, and explains why each constraint is required for verification. Also invoked by slci-inspection-incompatibility-analysis to fix constraints and obtain compatibility results. Trigger keywords: checkCompatibility, SLCI compatibility, code inspection readiness, Model Advisor compatibility report.
SLCI Compatibility Analysis
Determine whether a Simulink model's configuration and structure meet the requirements for SLCI (Simulink Code Inspector) code inspection.
When to Use
- User asks to check model compatibility for SLCI / Simulink Code Inspector
- User asks to run
checkCompatibilityor analyze compatibility results - User wants to know why a model is incompatible with code inspection
- User wants to understand what must be fixed before inspection can succeed
- Delegated from
slci-inspection-incompatibility-analysisto apply fixes or obtain compatibility results
When NOT to Use
- User already has inspection results (from
c.inspect()) and needs to trace failures to root causes, useslci-inspection-incompatibility-analysisinstead - User wants general Simulink model building or testing, use the core MBD skills
Boundary note: This skill covers the pre-inspection compatibility check
(checkCompatibility). The slci-inspection-incompatibility-analysis skill covers
post-inspection failure analysis (inspect results) and delegates back to this
skill for applying fixes and obtaining compatibility results. If a user simply asks
"is my model ready for SLCI?", use this skill.
Guardrails
- Never modify the original model. Copy to
<model_name>_fixed.slxfirst. Also copy any associated data dictionary (.sldd) or.matfiles if fixes require modifying them. All fixes are applied to the copy only. After copying, runfileattrib('<copy>', '+w')to ensure the copy is writable. - Always produce a Post-Fix Change Report after fixes are applied, so the user knows exactly what was changed.
