# Slci Compatibility Analysis

Use when you need to verify a Simulink model is compatible with SLCI code inspection...

- Repository: https://github.com/matlab/simulink-agentic-toolkit (1305 stars)
- Category: Engineering
- License: see repository
- Last updated: 2026-10-29
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add matlab/simulink-agentic-toolkit --skill slci-compatibility-analysis -g -a claude-code -y`
Codex: `npx skills add matlab/simulink-agentic-toolkit --skill slci-compatibility-analysis -g -a codex -y`
Cursor: `npx skills add matlab/simulink-agentic-toolkit --skill slci-compatibility-analysis -g -a cursor -y`
Gemini CLI: `npx skills add matlab/simulink-agentic-toolkit --skill slci-compatibility-analysis -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add matlab/simulink-agentic-toolkit`

## Description

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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# 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 `checkCompatibility` or 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-analysis` to 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, use `slci-inspection-incompatibility-analysis` instead
- 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

1. **Never modify the original model.** Copy to `<model_name>_fixed.slx` first.
   Also copy any associated data dictionary (`.sldd`) or `.mat` files if fixes
   require modifying them. All fixes are applied to the copy only.
   After copying, run `fileattrib('<copy>', '+w')` to ensure the copy is writable.
2. **Always produce a [Post-Fix Change Report](#post-fix-change-report)** after
   fixes are applied, so the user knows exactly what was changed.

## Domain Model: What SLCI Compatibility Means

The rest: https://github.com/matlab/simulink-agentic-toolkit/blob/HEAD/skills-catalog/code-generation/slci-compatibility-analysis/SKILL.md