SkillAgentSearch skills...

testing-simulink-models

Tests Simulink models using either ephemeral Gherkin-based tests (model_test) for quick validation or persistent tests (Simulink Test API) authored from requirements or behavioral specs. Requires Simulink Test.

Install / Use

npx skills add matlab/simulink-agentic-toolkit --skill testing-simulink-models

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

85/100

Category

Automation

Supported Platforms

Universal

Our assessment of testing-simulink-models

testing-simulink-models scores 85/100 on our quality scale, 1977th of 2,769 Automation skills we index.

Its SKILL.md is 6.2 KB long, well organised into 10 sections and no code examples: a thorough specification that gives an agent plenty to work with.

With 1,148 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
29/30
Structure
13/20
Description
15/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so testing-simulink-models is actively maintained.
  • Our last check on 2026-11-05 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-04. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

testing-simulink-models compared with similar skills

All 4 of these similar skills score higher than testing-simulink-models; compare them before choosing.

SkillScoreStarsUpdatedFormat
testing-simulink-models (this skill)by matlab851.1k2mo agoSKILL.md
Agent-Reachby Panniantong100112.7k9d agoCLAUDE.md
rufloby ruvnet10082.0ktodayCLAUDE.md
headroomby headroomlabs-ai10079.9ktodayCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10039.9k8d agoCLAUDE.md

Frequently asked questions

How do I install testing-simulink-models?
Run npx skills add matlab/simulink-agentic-toolkit --skill testing-simulink-models. The install tabs above show the steps for each supported agent.
Which AI agents does testing-simulink-models work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is testing-simulink-models safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is testing-simulink-models still maintained?
The repository was last updated about 2 months ago, so testing-simulink-models is actively maintained.

name: testing-simulink-models description: Tests Simulink models using either ephemeral Gherkin-based tests (model_test) for quick validation or persistent tests (Simulink Test API) authored from requirements or behavioral specs. Requires Simulink Test. license: https://www.mathworks.com/content/dam/mathworks/license/pmrl/license.md metadata: author: MathWorks version: "2.0"

Testing Simulink Models

Requires Simulink Test and R2023a or later. The requirement-driven entry point also requires Requirements Toolbox. The coverage workflow also requires Simulink Coverage. If Simulink Test is unavailable, use simulating-simulink-models with manual assertions.

When to Use

  • Writing pass/fail tests for a Simulink model or subsystem
  • Verifying expected behavior against requirements or acceptance criteria
  • Creating regression tests to catch future breakage
  • Reproducing and validating bug fixes with structured assertions
  • Collecting decision coverage metrics
  • Authoring persistent tests from linked requirements or a behavioral spec

When NOT to Use

  • Building or editing model structure → use building-simulink-models
  • Running simulations for data exploration, sweeps, or custom analysis → use simulating-simulink-models
  • Querying or resolving parameter values → use model_query_params / model_resolve_params
  • Creating or editing requirements → use generate-requirement-drafts
  • Injecting faults onto model signals without test authoring → use inject-faults
  • FMEA, FHA, FTA, or other safety analysis documents → use manage-safety-analysis
  • Simulink Test is not installed → fall back to simulating-simulink-models with manual assertions

Testing Approaches

This skill provides two testing approaches. Choose based on task context:

| | Gherkin (model_test) | Simulink Test API (test_create family) | |---|---|---| | Persistence | Ephemeral — harness discarded after session | Persistent — .mldatx files remain in project | | Speed | ~3s (draft mode) | ~60s (full Simulink Test infrastructure) | | Traceability | None | Full requirement linking via .slreqx | | Use case | Bug fixes, quick validation, agentic loop | Certification, systematic testing, formal V&V; also takes behavioral specs | | Approval needed | No | Yes — engineer reviews test plan before execution | | Coverage | coverage parameter ('none' or 'decision') | Via test_run options | | Toolbox | Simulink Test | Simulink Test (+ Requirements Toolbox for requirement path) |

→ For Gherkin testing, read references/gherkin-based-fast-testing.md → For Simulink Test API authoring (requirements / behavioral spec), read references/simulink-test-authoring.md

Workflow — Gherkin (Quick Validation)

  1. Understand the component: Use model_overview and model_read on the target subsystem to identify inputs, outputs, and expected behavior.
  2. Write the .feature file: Author a Gherkin test following the syntax in references/gherkin-based-fast-testing.md. Start with one scenario covering the primary nominal case.
  3. Cap StopTime before running: Check the model's StopTime with model_query_params. If it is inf (or unset/auto), you MUST pass a finite stop time to model_test — an infinite sim never returns and hangs MATLAB. Pick a finite value that lets the behavior settle (2–30s for a step response).
  4. Run in draft mode: Call model_test with draft_mode='true' for rapid iteration (~3s). Fix syntax or signal errors.
  5. Run full compilation: Once draft passes, re-run with draft_mode='false' to validate against the actual compiled model (catches type/dimension mismatches).
  6. Expand coverage: Add scenarios for edge cases, fault conditions, and boundary behavior. Use coverage='decision' to identify untested branches.

Workflow — Simulink Test API (Persistent)

  1. Understand the component: Use model_overview and model_read on the target subsystem to identify inputs, outputs, and expected behavior.
  2. Propose test plan → wait for approval: Present what to test, at what scope, and why. Do not call test_create until the engineer approves.
  3. Create test cases: Call test_create with the appropriate entry point — component/model only or requirement-driven (RequirementID + ReqSetPath). Pass TestFile as an absolute path under the working folder (never a bare filename — it would land in the skill's scripts/ dir, since that is the project_path). See references/simulink-test-authoring.md for call shapes.
  4. Propose test configuration → wait for approval: Present stop time, sim config, signal logging, assessments, and parameter overrides for each test case. Do not call test_edit until the engineer approves. Always set a finite StopTime via test_edit — if the model's StopTime is inf (or unset), the test run never returns and hangs MATLAB. Choose a finite value that lets the behavior settle (2–30s for a step response).
  5. Run and report: Call test_run, present pass/fail summary with assessment detail. Engineer decides next steps.

Guardrails

Always

  • Inspect model (model_overview / model_read) before writing tests — otherwise you write tests against wrong I/O
  • Report failures with assessment names, conditions, and signal summaries — users can't diagnose without detail
  • Never run a sim or test with StopTime=inf. Check StopTime before any model_test/test_run; if it is inf or unset, override it with a finite value first. An infinite sim never returns and hangs the MATLAB session (and, in a shared session, every subsequent task).

Never

  • Guess pass/fail criteria — ask the user if unclear
  • Change MATLAB working directory while a model is open — breaks harness cache

References

  • references/gherkin-based-fast-testing.md — Gherkin syntax, draft mode, coverage, Simscape constraints
  • references/simulink-test-authoring.md — API manual: setup, constraints, test_create entry shapes, edit/read/run signatures
  • references/assessment-format.md — LoggedSignals and Assessments struct formats
  • assets/test-structure-template.md — Test structure proposal template (requirement-driven path)
  • assets/test-config-template.md — Test configuration proposal template (requirement-driven path)

Copyright 2026 The MathWorks, Inc.


Related Skills

View on GitHub
GitHub Stars1.1k
CategoryAutomation
Updated2mo ago
Forks106

Languages

HTML

Trust signals

88/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium