# Slci Inspection Incompatibility Analysis

Use when SLCI code inspection has failed due to compatibility issues and you need to...

- 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-inspection-incompatibility-analysis -g -a claude-code -y`
Codex: `npx skills add matlab/simulink-agentic-toolkit --skill slci-inspection-incompatibility-analysis -g -a codex -y`
Cursor: `npx skills add matlab/simulink-agentic-toolkit --skill slci-inspection-incompatibility-analysis -g -a cursor -y`
Gemini CLI: `npx skills add matlab/simulink-agentic-toolkit --skill slci-inspection-incompatibility-analysis -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add matlab/simulink-agentic-toolkit`

## Description

Use when SLCI code inspection has failed due to compatibility issues and you need to diagnose the incompatibilities. Traces inspection failures back to root-cause incompatibility settings or known limitations by matching failed code lines against known incorrect code generation patterns and documented limitation scenarios. Hands off to slci-compatibility-analysis for fixes. Trigger keywords: inspect, inspection failed, trace inspection errors, why did inspection fail, SLCI verification failures, limitation.

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

# SLCI Inspection Incompatibility Analysis

Analyze SLCI code inspection results and trace failures back to compatibility
constraint violations or known limitations by matching failed code lines against
known incorrect code generation patterns and documented limitation scenarios.

## When to Use

- User asks why SLCI inspection failed or has verification errors
- User wants to trace inspection failures to their root-cause settings
- User has an inspection report with Failed/Error/Unverified items
- User asks to diagnose code inspection issues before re-running
- User wants to understand which compatibility settings caused inspection failure

## When NOT to Use

- User wants to check model compatibility *before* running inspection (no
  inspection failure context), use `slci-compatibility-analysis` instead
- User confirms the inspection failure is not related to a compatibility issue
- User wants general Simulink model building or code generation help

## Workflow

### 0. Clarify Intent

Ask the user whether the inspection failure might be related to a compatibility
issue before taking any other action. Do not search for files or run MATLAB
until the user confirms.

- **Yes** → proceed to Step 1.
- **No** → stop this skill.
- **Unsure** → explain what compatibility issues are and ask again.

### 1. Locate the Inspection Report

Get the report folder from MATLAB:

```matlab
c = slci.Configuration('<model_name>');
reportFolder = c.getReportFolder();
```

Look for `<model_name>_report.html` (or `.pdf`/`.doc`). If found, compare the
model's timestamp against the report's, warn if the report may be stale.

**If the report does NOT exist**, stop and warn the user. Suggest `c.inspect()`.
If the user explicitly asks to run inspection, first check whether generated code
is stale or missing and regenerate if needed before inspecting.

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