Unity UI Automation

What it does

When your agent uses it

• The user asks to find a UI element by name
• Click a UI element
• Run a short UI interaction sequence during testing
• Scene authoring

Example prompts

• “/unity-ui-automation”

Requirements

• Pre-approved tools (allowed-tools): Bash(unity-cli:*), Read, Grep, Glob

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

1. 1Find the target with namePattern or elementType.
2. 2Inspect current state before acting (visibility, interactability).
3. 3Perform one interaction at a time and re-check state when sequence matters.
4. 4Combine with unity-playmode-testing only when the UI depends on runtime state.

What it can do on your machine

Read from SKILL.md and the folder at commit 7f45d7a. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves these tools, so the agent can use them without asking each time:

  • Bash(unity-cli:*)
  • Read
  • Grep
  • Glob

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Unity UI Automation loads about 735 tokens when it runs, and up to ~1.2k if it reads all its reference files. Until then it costs about 102 tokens; SKILL.md has 239 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~102

When it runs · the whole SKILL.md, loaded when a task matches

~735

With references · SKILL.md plus every file in references/, read only if the agent opens them

~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from akiojin/unity-cli at commit 7f45d7a, republished under its MIT licence (© akiojin). 239 words, ~735 tokens.

name

unity-ui-automation

description

Automate Unity UI inspection and interaction with unity-cli. Use when the user asks to find a UI element by name or type, inspect button or input state, click a UI element, set a UI value, or run a short UI interaction sequence during testing. Do not use for scene authoring or general play-mode control without UI targeting; use `unity-scene-create` or `unity-playmode-testing` instead.

allowed-tools

Bash(unity-cli:*), Read, Grep, Glob

metadata.author

akiojin

metadata.version

0.3.1

metadata.category

ui

metadata.triggers

ui, canvas, button, click, input-field

metadata.siblings

unity-localization, unity-ui-toolkit-build, unity-playmode-testing, unity-scene-create

unity-cli raw find_ui_elements --json '{"namePattern":"Start","includeInactive":true}'
unity-cli raw get_ui_element_state --json '{"elementPath":"/Canvas/StartButton"}'
unity-cli raw click_ui_element --json '{"elementPath":"/Canvas/StartButton"}'
unity-cli raw set_ui_element_value --json '{"elementPath":"/Canvas/NameInput","value":"Player1"}'

© akiojin, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in .claude-plugin/plugins/unity-cli/skills/unity-ui-automation of akiojin/unity-cli.

• SKILL.md
• references/runtime-checklist.md
• references/ui-test-flow.md

Open the folder on GitHubat commit 7f45d7a