- name
SKILL.md
스킬 파일은 게시자의 저장소에 그대로 있습니다.
복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add matlab/simulink-agentic-toolkit --skill arranging-simulink-layouts -a cursor -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add matlab/simulink-agentic-toolkit --skill arranging-simulink-layouts -a claude-code -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add matlab/simulink-agentic-toolkit --skill arranging-simulink-layouts -a codex -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add matlab/simulink-agentic-toolkit --skill arranging-simulink-layouts -a grok -y복사한 메시지를 Grok Bot 채팅에 보냅니다. Bot이 GitHub에서 이 SKILL.md를 가져와 모든 Bot이 공유하는 스킬에 추가합니다.
Install this skill: https://github.com/matlab/simulink-agentic-toolkit/tree/HEAD/skills-catalog/model-based-design-core/arranging-simulink-layouts게시자 제공
Reposition blocks and reroute their lines 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 operation 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. Treat every existing diagram as hand-arranged, however messy it looks.
A vague request ("clean up the layout", "this looks messy") is not agreement to move every block. Only a user who accepts that the whole diagram will move has agreed. For a vague request, diagnose first:
evaluate_matlab_code. Touching blocks count as a problem too. Don't compare Position values by eye, because that misses pairs.
b = find_system('<scopePath>', 'SearchDepth', 1, 'Type', 'Block');
b = b(~strcmp(b, '<scopePath>'));
p = cell2mat(get_param(b, 'Position'));
pad = 5;
for i = 1:numel(b)
for j = i+1:numel(b)
if all(p(i,1:2) - pad < p(j,3:4)) && all(p(j,1:2) < p(i,3:4) + pad)
fprintf('%s and %s overlap or are closer than %d px\n', strrep(b{i}, newline, ' '), strrep(b{j}, newline, ' '), pad);
end
end
end
Also look for lines that run through blocks, and for a block far from every block it connects to, or outside the main body of the diagram.model_edit(model, "root", '[{"op":"layout","targets":["blk_5","blk_7"]}]', "incremental")
scope. Make one call per scope.Position values before and after. If any shifted, put them back and place the targets with configure instead.layout operation 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 when the user names a position, asks for specific alignment, or says every other block must stay where it is. In that last case, move each target along one axis into free space, and don't move it past a block it started clear of. That keeps the user's picture of the diagram intact.
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)
A selection can be stale: earlier operations sometimes leave blocks selected. Read the block names back to the user and confirm before laying out.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. After either operation, run no layout. Offer a full layout of the affected scope, and run it only if the user agrees.
layout operation, or with configure Position through model_edit, not with set_param block by block. set_param skips line rerouting and the model_edit pipeline.Simulink.BlockDiagram.arrangeSystem only when the user asks for Auto Arrange by name.Simulink.BlockDiagram.createSubsystem. Copying blocks in one at a time loses wiring and layout. After grouping or expanding, offer a full layout instead of running one.Copyright 2026 The MathWorks, Inc.
Arranges Simulink block diagram layout to improve readability using the model_edit layout engine. Use when the user asks to fix, clean up, tidy, straighten, or rearrange a layout, or to run Simulink's
---name: arranging-simulink-layoutsdescription: Arranges Simulink block diagram layout to improve readability using the model_edit layout engine. Use when the…---# skills-catalog/model-based-design-core/arranging-simulink-layouts/SKILL.md개요
Arranges Simulink block diagram layout to improve readability using the model_edit layout engine. Use when the user asks to fix, clean up, tidy, straighten, or rearrange a layout, or to run Simulink's Auto Arrange, when blocks overlap or lines cross, when specific blocks need repositioning, or when grouping blocks into or expanding a subsystem.
FAQ
게시자에게서 skills-catalog/model-based-design-core/arranging-simulink-layouts/SKILL.md를 다운로드하거나 경로를 복사해 저장소를 엽니다. PlugMCP는 스킬을 목록에 올릴 뿐 파일을 호스팅하지 않습니다.
게시자가 https://github.com/matlab/simulink-agentic-toolkit에서 관리합니다.
Claude, Cursor, Codex, Grok Build는 게시자의 저장소에서 추가한 SKILL.md를 읽을 수 있습니다. Grok Bot은 채팅에서 스킬의 GitHub 폴더 링크를 보내면 설치합니다.