SkillAgentSearch skills...

simulink-compose-multi-vehicle-system

Use this skill to build or configure a multi-vehicle aerospace simulation in Simulink with Aerospace Blockset system-level actor models and mission planning functions: fleet simulations, multi-UAV missions, formation flights, search and rescue missions, coordinated aircraft and ship scenarios, or an…

Install / Use

npx skills add matlab/simulink-agentic-toolkit --skill simulink-compose-multi-vehicle-system

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

90/100

Supported Platforms

Universal

Tags

Our assessment of simulink-compose-multi-vehicle-system

simulink-compose-multi-vehicle-system scores 90/100 on our quality scale, 1407th of 4,716 Development & Engineering skills we index (top 30%).

Its SKILL.md is 15 KB long, well organised into 13 sections with 1 code example: 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
30/30
Structure
17/20
Description
15/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so simulink-compose-multi-vehicle-system is actively maintained.
  • 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-11-19. Automated pattern scan on 2026-11-19. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

simulink-compose-multi-vehicle-system compared with similar skills

All 4 of these similar skills score higher than simulink-compose-multi-vehicle-system; compare them before choosing.

SkillScoreStarsUpdatedFormat
simulink-compose-multi-vehicle-system (this skill)by matlab901.1k2mo agoSKILL.md
taste-skillby Leonxlnx100118.9k11d agoCLAUDE.md
hyperframesby heygen-com10087.1ktodayCLAUDE.md
ai-job-searchby ai-job-search-dev10072.6ktodayCLAUDE.md
claude-howtoby luongnv8910047.5k5d agoCLAUDE.md

Frequently asked questions

How do I install simulink-compose-multi-vehicle-system?
Run npx skills add matlab/simulink-agentic-toolkit --skill simulink-compose-multi-vehicle-system. The install tabs above show the steps for each supported agent.
Which AI agents does simulink-compose-multi-vehicle-system 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 simulink-compose-multi-vehicle-system 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 simulink-compose-multi-vehicle-system still maintained?
The repository was last updated about 2 months ago, so simulink-compose-multi-vehicle-system is actively maintained.

name: simulink-compose-multi-vehicle-system description: > Use this skill to build or configure a multi-vehicle aerospace simulation in Simulink with Aerospace Blockset system-level actor models and mission planning functions: fleet simulations, multi-UAV missions, formation flights, search and rescue missions, coordinated aircraft and ship scenarios, or any model where several vehicles share one scene. Also use it to plan a mission or generate trajectories with Aero.trajectory functions (waypoints, search patterns, loiters, transits) or to configure Kinematic Aerospace Actor blocks, even when the request does not say "multi-vehicle". The skill covers scene setup, trajectory generation, coordination logic, architecture decomposition, and coordinate frame consistency. Requires MATLAB R2026b or later. license: https://www.mathworks.com/content/dam/mathworks/license/pmrl/license.md metadata: author: MathWorks version: "1.2"

Compose Multi-Vehicle Systems

Build multi-vehicle scenes with the Kinematic Aerospace Actor block and the Aero.trajectory functions in Aerospace Blockset.

Requires MATLAB R2026b or later; the Kinematic Aerospace Actor block and several Aero.trajectory functions first ship in R2026b. Before anything else, check the release with isMATLABReleaseOlderThan("R2026b"). If it returns true, tell the user this skill needs R2026b or later and stop.

When to Use

  • Several vehicles (aircraft, UAVs, agile aerial vehicles, ships) share one Simulink scene.
  • The task is a coordinated mission: surveillance, formation, coverage, escort, or search and rescue.
  • Reference trajectories must drive vehicle models.
  • The request names the Kinematic Aerospace Actor block or Aero.trajectory functions.

When NOT to Use

  • One vehicle with detailed aerodynamics: use 6DOF blocks or a custom plant.
  • 3D visualization: out of scope.
  • Wind and atmosphere effects: out of scope. Scenes assume calm air.
  • Model-building mechanics (block placement, wiring, running simulations): delegate to the companion skills below.

| Companion skill | Skill group | Delegate for | |-----------------|-------------|--------------| | building-simulink-models | Model-Based Design Core | Block placement, wiring, bus configuration, data dictionary API | | building-architecture-models | Model-Based System Engineering | System Composer models, components, ports | | managing-simulink-projects | Model-Based Design Core | MATLAB Project creation, paths, startup and shutdown | | simulating-simulink-models | Model-Based Design Core | Running sim, SimulationInput, logged data | | simulink-run-parallel-simulations | Simulink Simulation | Parameter sweeps with parsim, batchsim, DesignStudy | | testing-simulink-models | Verification, Validation & Test | Test harnesses and regression tests |

Model-Based Design Core installs by default. If a companion skill from another group is not installed, name the group to install. For example, scenes with three or more vehicles use building-architecture-models from Model-Based System Engineering.

Workflow

  1. Collect the Required Inputs. Verify: every row of the table below has a value.
  2. Decompose the architecture with System Composer (3+ vehicles or a complex mission). Verify: each component maps to one referenced model.
  3. Create the MATLAB Project with the required folders. Verify: the project opens and its startup runs without errors.
  4. Generate the data dictionary with code: bus objects, fleet parameters, simulation settings. Verify: every bus object the actor blocks name exists in the dictionary.
  5. Create one vehicle model per vehicle with one Kinematic Aerospace Actor block. Verify: the model compiles on its own.
  6. Generate trajectories with Aero.trajectory and load them for each vehicle. Verify: plot each trajectory before you wire it.
  7. Wire coordination and integrate. Verify: the frame check and compile check in § Validation pass.
  8. Simulate and check intent. Verify: the mission-intent check in § Validation passes.

Required Inputs

| Input | Ask or derive | Rule | |-------|---------------|------| | Number of vehicles | ASK if not given | It cannot be inferred safely | | Vehicle types | DERIVE | "UAV/aircraft" → Fixed Wing. "ship/boat" → Surface Vehicle. "agile/high-maneuver vehicle" → Agile Aerial Vehicle. ASK if ambiguous | | Mission type | DERIVE | "patrol" → surveillance. "fly together" → formation. "search area" → coverage. "protect" → escort. ASK if unclear | | Coordinate frame | DERIVE | Local area under about 50 km → Flat Earth. Global routes, or positions given as latitude and longitude → WGS84 Ellipsoid | | Trajectory type | DERIVE | See § Trajectory Selection. ASK only when two options fit equally well | | Fidelity | DERIVE | Kinematic by default. Redirect if the user asks for aerodynamics or 6DOF | | Mission area (coverage, search, patrol) | ASK if no size or location is given | It sets the trajectory geometry. A guessed area wastes the build |

List every derived value in your response so the user can override it, then continue.

Guardrails

Always

  1. Get all seven Required Inputs before you build. A wrong vehicle count or frame forces a rebuild.
  2. Put each vehicle in its own .slx and use it through Model Reference. Separate models compile in parallel, test alone, and scale.
  3. Make a System Composer architecture model the top level for 3+ vehicles or a complex mission (several coordination modes, sensor interactions, or mixed vehicle types). It keeps the interfaces between vehicles and coordination explicit. Expressing the architecture only in a build script does not satisfy this rule.
  4. Use the same frame for every actor and trajectory. A mismatch runs without error and gives wrong relative positions.
  5. Define a bus object for every actor port before you compile. The block ships with a placeholder bus name, so compile fails until you set real bus objects.
  6. Generate the data dictionary (.sldd) with code and keep fleet parameters, bus objects, and settings in it. Never create entries in the GUI. A scripted dictionary is reproducible and reviewable.
  7. Organize the work as a MATLAB Project. The root holds only the .prj file, README.md, buildLog.md, and the folders models/ (all .slx), data/ (.sldd), utilities/ (all .m), and work/ (cache). A fixed layout lets the user find every file.
  8. Put coordination in Stateflow, in its own referenced model, and make its output change vehicle motion. A flag that nothing reads is not coordination.
  9. Keep a run log while you work, and write a README when the build works. The log makes a long build reviewable and resumable.

Ask First

  • Before you skip or change any Always rule. Give the rule number, the reason, and your alternative. The user cannot review a decision that is already built, and finding it later costs them rework.
  • When the mission type is not in the Required Inputs table and the request needs coordination.
  • When a rule costs a lot of effort. Cost is a reason to ask, never a reason to decide alone.

Never

  • Never build the simulation as a MATLAB script. Use scripts only for setup and analysis.
  • Never hand-roll kinematics with Integrator or MATLAB Function blocks. Use the actor block.
  • Never use MATLAB Function blocks for coordination logic.
  • Never build first and report a deviation afterward. An unapproved deviation is a violation.
  • Never clamp or saturate an output to hide a wrong value. Fix the parameter that caused it.
  • Never rely on automatic signal names at bus boundaries. Name every signal explicitly.
  • Never write to the shared dictionary inside a parallel sweep. Override parameters per simulation instead.

Key Functions

| Function or block | Purpose | Toolbox | Available From | |-------------------|---------|---------|----------------| | Kinematic Aerospace Actor | Kinematic motion, inertial sensing, and target tracking for one vehicle | Aerospace Blockset | R2026b | | Aero.trajectory.polylineTrajectory | Straight legs between waypoints | Aerospace Blockset | R2026a | | Aero.trajectory.bezierTrajectory, polynomialTrajectory, circularTrajectory | Smooth transit between two points | Aerospace Blockset | R2026a | | Aero.trajectory.parallelSweepTrajectory, creepingTrajectory, expandingSquareTrajectory, sectorTrajectory, tracklineTrajectory | Search patterns | Aerospace Blockset | R2026a | | Aero.trajectory.lissajousTrajectory, spaceFillingTrajectory | Coverage patterns | Aerospace Blockset | R2026b | | Aero.trajectory.merge | Join two trajectories with a smooth transition | Aerospace Blockset | R2026b | | Aero.trajectory.addEvent | Add named events to a trajectory | Aerospace Blockset | R2026a |

Trajectory Selection

| Mission intent | Use | |----------------|-----| | Transit through waypoints (default) | polylineTrajectory | | Smooth transit between two points | bezierTrajectory or polynomialTrajectory | | Perimeter patrol, loiter, orbit, or transit with turn-radius limits | circularTrajectory | | Area search | parallelSweepTrajectory, creepingTrajectory, expandingSquareTrajectory, sectorTrajectory, tracklineTrajectory | | Area coverage (R2026b) | lissajousTrajectory, spaceFillingTrajectory | | Join two segments of the same family | PriorTrajectory on the new segment | | Join a smooth segment and a waypoint segment | merge (R2026b). PriorTrajectory does not support mixing the families |

ref = Aero.trajectory.parallelSweepTrajectory( ...
    DatumPoint=[100 50], Bearing=pi/4, ...
    FieldLength=500, FieldWidth=200, TrackSpacing=25, ...
    Speed=15, Altitude=100);

The output is a struct of timeseries: xNorth, yEast, Speed, Altitude, Heading, FlightPathAngle, WaypointIndex. Run help Aero.trajectory.<name> for exact arguments. Read references/mission-planning-reference.md for arguments, gotchas, and packing.

Actor Selection

| Vehicle role | Actor type | Controlled channels | |--------------|------------|---------------------| | Aircraft, fixed-wing UAVs (default) | Fixed Wing | Speed, flight path angle, heading or bank | | High-maneuver aerial vehicles, agile UAVs | Agile Aerial Vehicle | Speed, lateral and vertical acceleration | | Ships, ground vehicles | Surface Vehicle | Speed, heading |

| Scene | Navigation frame | |-------|------------------| | Local, under about 50 km (default) | Flat Earth | | Latitude and longitude inputs or outputs | WGS84 Ellipsoid | | Earth-centered Cartesian positions | ECEF Frame |

Read references/frame-consistency-rules.md when you set up a scene or debug distances and positions.

Use model_query_params with params: ["all"] on an actor block to read its parameters and valid values. Read references/actor-models-reference.md for ports, buses, dynamics, and the tracker.

Gotchas

  • Bearing, AbsoluteBearing, and RelativeBearing are in RADIANS.
  • parallelSweepTrajectory takes FieldLength, FieldWidth, TrackSpacing. It has no SweepWidth or LegSpacing.
  • Altitude has no default on the waypoint and search functions. Omitting it errors.
  • Search patterns require DatumPoint and Bearing.
  • A vector argument (for example Speed=[15 20 25]) returns a cell array, one trajectory per element. Index it with traj{k}.
  • Only polylineTrajectory takes CoordinatePlane. All other functions output Flat Earth NED.
  • Trajectory angles are radians. The actor reads angles in its Attitude units (default Degrees). Convert when you pack the signals.
  • Declare the unit convention once, in the data dictionary. Store each angle parameter in the unit of the layer that reads it, and check units at every boundary. Never assume they match.
  • Hold the last trajectory value until the simulation stop time. Otherwise the reference signal ends early.
  • Bus element O

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars1.1k
CategoryDevelopment
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