- name
SKILL.md
Le fichier du skill reste dans le dépôt de l'éditeur.
Collez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add matlab/simulink-agentic-toolkit --skill simulink-compose-multi-vehicle-system -a cursor -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add matlab/simulink-agentic-toolkit --skill simulink-compose-multi-vehicle-system -a claude-code -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add matlab/simulink-agentic-toolkit --skill simulink-compose-multi-vehicle-system -a codex -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add matlab/simulink-agentic-toolkit --skill simulink-compose-multi-vehicle-system -a grok -yEnvoyez le message copié dans un chat Grok Bot. Le Bot récupère ce SKILL.md sur GitHub et l'ajoute aux skills que partagent tous vos Bots.
Install this skill: https://github.com/matlab/simulink-agentic-toolkit/tree/HEAD/skills-catalog/aerospace/simulink-compose-multi-vehicle-systemDe l'éditeur
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.
Aero.trajectory functions.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.
Aero.trajectory and load them for each vehicle.
Verify: plot each trajectory before you wire it.List every derived value in your response so the user can override it, then continue.
Always
.slx and use it through Model Reference. Separate models compile in parallel, test alone, and scale..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..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.Ask First
Never
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.
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.
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.DatumPoint and Bearing.Speed=[15 20 25]) returns a cell array, one trajectory per element. Index it with traj{k}.polylineTrajectory takes CoordinatePlane. All other functions output Flat Earth NED.None. Set it to Tracker, or no target is ever detected.references/architecture-components.md § Per-Instance Data.Feed each vehicle's Actor States bus into the chart. Feed the chart's mode or
phase output back into each vehicle model, and select that vehicle's reference
from it. Use temporal logic (after(N, sec)), never manual counters. Read
references/coordination-patterns.md for each pattern.
Run these checks through the MCP tools after you build or change a model.
Mission intent. Before you build, write down the numbers the scenario must produce: closest-approach distances and times, mode-change times, detection windows. After simulation, compare the results against them. "It compiles" is not a pass criterion.
Before you report complete, mark each Always and Never rule as yes, approved deviation (with the user's approval), or VIOLATION. "Partly" counts as a violation. Name every violation in the report and do not call the task complete. Do not hide a violation as a design note, an "as-built deviation", or a known limitation.
Offer both at the start of the task.
buildLog.md, updated as you work): the plan, the action history, each error and its fix, inputs and corrections from the user, and each approved deviation with its rule number, the user's decision, and the date.README.md): what each folder holds, how to run the simulation, and how to change fleet size, a trajectory, or a controller.Read references/common-mistakes.md when a model misbehaves or a build step fails.
Copyright 2026 The MathWorks, Inc.
>
---name: simulink-compose-multi-vehicle-systemdescription: >---# skills-catalog/aerospace/simulink-compose-multi-vehicle-system/SKILL.mdFAQ
Téléchargez skills-catalog/aerospace/simulink-compose-multi-vehicle-system/SKILL.md auprès de l'éditeur, ou copiez le chemin et ouvrez le dépôt. PlugMCP répertorie le skill et n'héberge pas le fichier.
L'éditeur le maintient sur https://github.com/matlab/simulink-agentic-toolkit.
Claude, Cursor, Codex et Grok Build peuvent lire un SKILL.md que vous ajoutez depuis le dépôt de l'éditeur. Grok Bot l'installe lorsque vous envoyez dans un chat le lien du dossier GitHub du skill.