Author Modeladvisor Checks
Author or upgrade Model Advisor checks for Simulink and System Composer models.
Install
npx skills add matlab/simulink-agentic-toolkit --skill author-modeladvisor-checks -g -a claude-code -y- Repository
- matlab/simulink-agentic-toolkit1.3k
- Category
- Testing
- Updated
- 6d ago
- License
- See repository
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Author or upgrade Model Advisor checks for Simulink and System Composer models. Covers the full lifecycle: guideline authoring, check specification, Model Advisor check implementation, and qualification testing. Use when creating new checks (edit-time, standard batch, config-parameter, auto-fix), converting legacy StyleOne/StyleTwo/StyleThree checks to modern DetailStyle, creating a guideline for modeling, enforcing a modeling rule, or testing/qualifying a check. Triggers on any modeling constraint (e.g., "blocks shall...", "signals must match...", "parameters shall be set to...").
Author Model Advisor Check
When to Use
- User provides any modeling constraint (e.g., "blocks shall...", "signals must match...")
- User asks to create a guideline for modeling
- User asks to author, implement, or write a Model Advisor check
- User asks to test, qualify, or validate a custom check
- User mentions "enforce", "standard", "compliance rule", or "modeling rule"
When NOT to Use
- Post-hoc compliance checking of existing models, use
checking-model-compliance - General model building without enforcement context, use
building-simulink-models - Running existing checks or viewing results, use Model Advisor directly
CRITICAL: REVIEW GATES
You are a state machine that controls the ENTIRE workflow. Procedure reference files describe how to execute each step, you read them for details and execute their procedures inline.
There are 3 REVIEW GATES and 1 CONDITIONAL GATE where you pause and ask the user to choose before continuing. If the user provides feedback, incorporate it. If the user selects the recommended option, continue immediately.
If the user's prompt includes "proceed without asking", "skip confirmation", "without asking for confirmation", or similar, skip ALL review gates and proceed through the entire workflow without stopping. Do NOT use AskUserQuestion or any interactive tool in this mode.
Review Gates (use descriptive names, NEVER say "Gate 1", "Gate 2", "Gate 3"):
- Guideline ID & Scope Review, after deriving IDs and before writing the guideline
- Check Specification Review, after generating the check specification, before implementing
- Test Plan Review, after generating the test specification, before implementing tests
