Studio Assistant UI Operations Guide
Apps & Automationstudio-assistant-ui-operations-guideStudio Assistant UI Operations Guide is an Agent Skill for apps & automation published in the apm-studio/apm-studio repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Tells the APM Studio Assistant how to open, reveal, inspect, hide, show, move, resize, and panel-toggle UI surfaces through apply_studio_actions. Use for direct UI manipulation requests.
QUICK START
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/apm-studio/apm-studio/blob/HEAD/server/services/studio-assistant/skills/studio-assistant-ui-operations-guide/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/studio-assistant-ui-operations-guide, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
APM Studio UI Operations Guide
Use this skill when the user asks APM Assistant to manipulate the APM Studio interface.
When To Use
- Open, show, reveal, select, focus, or inspect an Agent, Team, or draft.
- Open or close Packages, Workspace Tracking, or Terminal.
- Hide or show an Agent or Team.
- Move, resize, align, or arrange Agent/Team canvas windows.
Action Choices
showAgent: select/reveal an Agent, or open its editor withsurface: "editor".showTeam: select/reveal a Team, or open its editor withsurface: "editor".showDraft: open an Instruction or Skill draft editor.setStudioPanel: togglepackages,workspaceTracking, orterminal.setStudioNodeVisibility: set visible/hidden state for an Agent or Team.setStudioNodeFrame: set absolutepositionand/orsizefor an Agent or Team.
Targeting Rules
- Prefer exact ids from the snapshot.
- Use exact names only when ids are not needed or the target is unambiguous.
- Use same-call refs only for objects created earlier in the same tool call.
- Ask a short clarifying question if multiple visible objects match the user's target.
Surface Rules
- For
showAgentandshowTeam, omitsurfaceor usesurface: "canvas"for simple show/reveal requests. - Use
surface: "editor"only when the user asks to edit, configure, inspect settings, or fix readiness. - For
showTeameditor requests:editorMode: "team"for general Team editingeditorMode: "participant"withparticipantKeyeditorMode: "relation"withrelationId
Geometry Rules
- Use
setStudioNodeFrameonly when the snapshot provides current position and size or the user gives explicit coordinates/size. - Use absolute canvas coordinates.
- Do not invent geometry for subjective layout requests; ask if the desired arrangement is unclear.
- UI-only changes are hot Studio state. Do not describe them as packaged, saved, installed, or runtime-affecting.
Examples
{"version":1,"actions":[{"type":"showAgent","agentName":"Writer","surface":"editor"}]}
{"version":1,"actions":[{"type":"setStudioPanel","panel":"packages","open":true}]}
{"version":1,"actions":[{"type":"setStudioNodeFrame","nodeType":"team","teamName":"Review Flow","position":{"x":320,"y":240},"size":{"width":520,"height":460}}]}