Clean up Simulink block diagram layouts when blocks overlap, lines cross, or newly added blocks look out of place. It can rearrange selected blocks, tidy a whole scope when requested, set specific positions, and group blocks into or expand a subsystem.
Arranges and tidies Simulink block diagram layouts with the model_edit layout engine. Use when the user asks to fix, clean up, tidy, straighten, or rearrange a layout, when blocks overlap or lines cross, when specific blocks need re-placing, or when grouping blocks into or expanding a subsystem.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Re-place blocks with the SATK layout engine in model_edit. Move as little of the user's diagram as the request allows.
building-simulink-models. Layout already runs automatically after every model_edit call.layout op is Simulink-only. A chart scope accepts only a full re-layout (operations [], layout_mode "full"), which moves every element, so ask first.Selective layout is the default. A full layout of a diagram the user has arranged by hand discards their arrangement, so ask before running one.
| Situation | Method |
|---|---|
| A few blocks are messy, overlapping, or just added | {"op":"layout","targets":[...]} with layout_mode "incremental" |
| The whole scope is a mess and the user agrees that everything moves | operations [] with layout_mode "full" |
| The user explicitly asks for Simulink's own tidy-up | Format > Auto Arrange / Simulink.BlockDiagram.arrangeSystem, and only on request |
| The user wants an exact placement | configure with Position through model_edit |
model_edit(model, "root", '[{"op":"layout","targets":["blk_5","blk_7"]}]', "incremental")
scope. Make one call per scope.layout op with edits in the same call. A #ref target names a block that the call adds:
[{"op":"add_block","type":"Gain","ref":"g"},{"op":"connect","target":"blk_3.y1 -> #g.u1"},{"op":"layout","targets":["#g","blk_9"]}]targets.layout_mode "full", the targets are ignored and the whole scope is re-laid out.model_edit(model, "blk_12", "[]", "full")
Use it for a scope that is new or already unreadable, and only with the user's agreement. Prefer the smallest subsystem that contains the mess over root.
model_edit(model, "root", '[{"op":"configure","target":"blk_5","params":{"Position":"[300 100 340 130]"}}]', "incremental")
Later incremental layouts leave the block where you put it, but a full layout of the scope moves it. Use this only when the user names a position or asks for specific alignment.
blk_X IDs with model_read (depth "0") or model_overview on the scope.sel = find_system('<scopePath>', 'SearchDepth', 1, 'Type', 'Block', 'Selected', 'on');
ids = cellfun(@(p) ['blk_' extractAfter(Simulink.ID.getSID(p), ':')], sel, 'UniformOutput', false)
Position values with model_query_params, or check the model in the editor.layout: block in the response. applied: false comes with a detail that explains why. Report it; don't retry blindly.model_check(model, scope, '["unconnected_lines"]') to confirm that the wiring survived.To group blocks into a new subsystem, or expand a subsystem in place, see references/subsystem-restructuring.md. Don't rebuild the content block by block with model_edit.
set_param(..., 'Position', ...) block by block to "fix" a layout. Use a layout op, or configure Position through model_edit.Simulink.BlockDiagram.arrangeSystem when the user didn't ask for Auto Arrange.Simulink.BlockDiagram.createSubsystem.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Create or upgrade Model Advisor checks for Simulink and System Composer rules. The workflow covers guideline writing, check specifications, implementation, and qualification tests, including converting legacy check styles to the modern DetailStyle format.
Create synthetic waveforms such as steps, ramps, sine waves, chirps, pulses, and noise for Simulink inports. Populate an External Inputs or Signal Editor Dataset while preserving signal types, dimensions, units, and interpolation metadata, including timing for trigger and function-call inputs.
Build and refine system architecture models in System Composer across functional, logical, and physical layers. Define interfaces and stereotypes, create views and sequence diagrams, link layers through allocations, and trace requirements to components.
Build and edit Simulink, System Composer, Stateflow, and Simscape models by changing blocks, parameters, connections, architecture components, or chart internals. The workflow checks the resulting structure and flags unconnected ports or dangling lines.
Run Model Advisor checks on a Simulink model against supported standards such as MISRA, JMAAB, ISO 26262, and DO-178C. Get prioritized findings and suggested fixes; for JMAAB and MAB, add an AI review of guidelines that automated checks cannot fully assess.
Set up or update `.satk/block-policy.json` to control which Simulink blocks an agent may use, which it must exclude, and which block parameters it must leave unchanged. The skill validates policy settings before saving.