Fix Sldv Incompatibility
Use when a Simulink model is incompatible with Simulink Design Verifier (sldvcompat...
Install
npx skills add matlab/simulink-agentic-toolkit --skill fix-sldv-incompatibility -g -a claude-code -y- Repository
- matlab/simulink-agentic-toolkit1.3k
- Category
- Design
- Updated
- 6d ago
- License
- See repository
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Use when a Simulink model is incompatible with Simulink Design Verifier (sldvcompat returns false, or an SLDV analysis errors out on an unsupported construct) and needs to be made analyzable. Diagnoses the incompatibility, applies the matching fix to a copy, and confirms the copy is compatible; optionally raises confidence the fix preserved behavior via a back-to-back consistency replay (agreement on the generated tests, not a proof of equivalence). Do NOT use for running test generation, design error detection, or requirement verification themselves, only for making a model compatible so those can proceed.
SLDV Incompatibility Fixer
Fix Simulink Design Verifier incompatibilities by diagnosing the model and applying the matching fix. Block-level fixes go through model_edit; solver/config-level fixes are the one exception that requires setting the parameter directly (see Step 3).
When to Use
- User asks "why is my model incompatible with SLDV?"
- User asks "make this model compatible with SLDV"
- User asks to fix SLDV incompatibility issues
- User runs
sldvcompatand getsfalse - A test-generation or design-error-detection run errors out on an unsupported construct, and the user asks to get past it, make the model analyzable first, then hand back to that workflow
When NOT to Use
- The model is already compatible (
sldvcompatreturnstrue), there is nothing to fix. - The task is to run an SLDV analysis mode (test generation, design error detection, property proving) on an already-compatible model, use the corresponding analysis skill, not this one.
- The incompatibility is intended and the user wants to keep the unsupported construct, do not silently rewrite the model.
- The request is a general Simulink modeling edit unrelated to SLDV compatibility.
Scope
The core job is diagnose → fix → confirm compatible (Steps 1, 4). That is the default endpoint. Running an SLDV analysis mode (test generation, design error detection) and verifying behavior on the original model is optional and only happens when the surrounding intent calls for it (Step 5). A user who just wants compatibility gets the fix and nothing more.
