resolve-design-errors
Use when asked to run Design Error Detection (quick defect scan), find design errors in a Simulink model, perform root cause analysis on DED findings, fix division-by-zero, overflow, dead logic or out-of-bounds defects detected by SLDV, or diagnose why missing coverage cannot be achieved (dead logic blocking coverage objectives). Do NOT use for requirement verification, test generation, Inf/NaN detection, active logic analysis, or coverage measurement.
npx skills add matlab/simulink-agentic-toolkit --skill resolve-design-errors --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Detecting Design Errors (SLDV DED + Root Cause Analysis) ## When to Use - User asks to **check a Simulink model for design errors** (division-by-zero, overflow, dead logic, out-of-bounds) - User asks to **find root causes** of DED findings - User asks to **fix** or **understand** an analysis finding - User asks **why there is missing coverage** due to dead logic (dead logic gates prevent coverage objectives from being satisfied) - User has SLDV artifacts (`.mat` file) and wants analysis without re-running DED ## When NOT to Use - **Requirement verification** — checking if a model satisfies a requirement - **Test generation or test authoring** — creating test cases from requirements or for coverage - **Comprehensive verification** — this skill is a quick defect scan, not an exhaustive proof; a clean result does not guarantee the model is free of all errors - **Coverage measurement** — this skill does not measure or report model coverage; use Simulink Coverage tools ## Safety Rules 1. **Never patch the original model directly.** Always clone first before applying any fix. 2. **NEVER apply fixes without explicit user approval.** After root cause analysis, present findings and *sugge
- When to Use
- When NOT to Use
- Safety Rules
- Prerequisites
- Workflow
- Step 1 — Detect errors
- Step 2 — Root cause errors
- Step 3 — Classify errors (dead logic)
- Step 4 — Fix errors
- Common Mistakes
What does the resolve-design-errors skill do?
Use when asked to run Design Error Detection (quick defect scan), find design errors in a Simulink model, perform root cause analysis on DED findings, fix division-by-zero, overflow, dead logic or out-of-bounds defects detected by SLDV, or diagnose why missing coverage cannot be achieved (dead logic blocking coverage objectives). Do NOT use for requirement verification, test generation, Inf/NaN detection, active logic analysis, or coverage measurement.
How do I install it?
Run `npx skills add matlab/simulink-agentic-toolkit --skill resolve-design-errors --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From matlab/simulink-agentic-toolkit, a repository with 903 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.