Agent skill · Code Review & Quality

checking-model-compliance

Use this skill when the user asks to check Simulink model compliance against a standard (MISRA, MAB, JMAAB, ISO 26262, ISO 25119, DO-178C, DO-254, IEC 61508, IEC 62304, EN 50128, CERT C/CWE, AUTOSAR), wants to run Model Advisor checks, or needs a compliance report with fix suggestions. For JMAAB/MAB, supplement deterministic checks with agentic review of uncheckable guidelines.

matlabgithub.com/matlabGitHub ↗
claude-codecodexcopilotNOASSERTION
Install
npx skills add matlab/simulink-agentic-toolkit --skill checking-model-compliance --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 9
SKILL.md size: 9 KB
Bundled scripts: none
Version: 0.5
Declared author: MathWorks
Path: skills-catalog/verification-validation-and-test/checking-model-compliance/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 903
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Checking Model Compliance Runs Model Advisor checks for a named standard (or default configuration) and delivers a prioritized summary with fix suggestions. ## When to Use - Checking whether a Simulink model complies with a standard (MISRA, MAB, JMAAB, ISO 26262, DO-178C, etc.) - Running Model Advisor checks against a named compliance standard - Generating a compliance report with prioritized findings and fix suggestions - Running a custom Model Advisor configuration file against a model - Justifying or waiving specific compliance violations ## When NOT to Use - **Building or editing model structure** → `building-simulink-models` - **Writing behavioral tests** → `testing-simulink-models` - **Structural validation only (unconnected ports)** → `model_check` tool directly - **General model quality questions** without a named standard (e.g., "is my model well decomposed?") — this requires a different workflow ## Supported Standards | Standard | Accepted Inputs | |----------|----------------| | MISRA C:2023 | `MISRA_C`, `MISRA C`, `MISRA` | | MISRA Simulink/Stateflow | `MISRA_SLSF`, `MISRA Simulink` | | MAB | `MAB`, `MAAB` | | JMAAB v5.1 | `JMAAB` | | JMAAB v6 | `JMAAB_V6`, `JMAAB06`

What's inside
Steps it walks through
  1. When to Use
  2. When NOT to Use
  3. Supported Standards
  4. Custom Checks and Configurations
  5. Prerequisites
  6. Workflow
  7. 1. Identify Standard, Model, and Scope
  8. 2. Choose Path
  9. 3. Resolve Checks (Path A only)
  10. 4. Run Checks
  11. 5. Analyze Findings
  12. 6. Present Compliance Report
  13. 7. Agentic Review of Uncheckable Guidelines (JMAAB/MAB only)
  14. 8. Fix Mode
Ships with 8 files
  • manifest.yaml
  • references/fix-mode.md
  • references/semantic-evaluation-index.md
  • references/uncheckable-guidelines-review.md
  • scripts/detect_default_config.p
  • scripts/model_advisor_justify.p
  • scripts/model_advisor_resolve_checks.p
  • scripts/model_advisor_run.p
More from simulink-agentic-toolkit
All skills →
About this skill
What does the checking-model-compliance skill do?

Use this skill when the user asks to check Simulink model compliance against a standard (MISRA, MAB, JMAAB, ISO 26262, ISO 25119, DO-178C, DO-254, IEC 61508, IEC 62304, EN 50128, CERT C/CWE, AUTOSAR), wants to run Model Advisor checks, or needs a compliance report with fix suggestions. For JMAAB/MAB, supplement deterministic checks with agentic review of uncheckable guidelines.

How do I install it?

Run `npx skills add matlab/simulink-agentic-toolkit --skill checking-model-compliance --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.

Keep going