# Unity Editor Tools

> Inspect and control Unity Editor state with unity-cli. Use when the user asks to ping the editor, read console output, inspect or update a project setting, run a menu item, inspect windows or selection, manage packages, or capture profiler data. Do not use for scene authoring or asset edits; use `unity-scene-create`, `unity-asset-management`, or `unity-csharp-edit` for those workflows.

- Skill: `akiojin/unity-editor-tools` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add akiojin/unity-editor-tools`
- Raw SKILL.md: https://api.skillmd.com/api/skills/akiojin/unity-editor-tools/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: akiojin (https://skillmd.com/u/akiojin)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/akiojin/unity-editor-tools

---


# Editor Tools

Use this skill for editor-wide diagnostics and control: console, project settings, menu items, windows, selection, package manager, and profiler. Hand off to a domain skill once the request narrows to scene, asset, or code work.

## Use When

- The user asks for editor health checks, console logs, or profiler data.
- The user wants to inspect or change a project setting.
- The user wants to run a menu item, inspect windows, or manipulate the current selection.
- The user wants package manager or registry operations from the editor side.

## Do Not Use When

- The task is primarily about a specific scene or prefab; use `unity-scene-create` or `unity-prefab-workflow`.
- The work is asset import or material edits; use `unity-asset-management`.
- The work is a C# refactor; use `unity-csharp-edit`.
- The user only needs Play Mode or test execution; use `unity-playmode-testing`.

## Preferred Flow

1. Verify connectivity with `unity-cli system ping` and `get_editor_state`.
2. Read state before mutating it: console before clearing, settings before updating, profiler status before start/stop.
3. Apply one editor-wide change at a time and verify the result immediately.
4. Capture before/after state when project settings or packages change.

```bash
unity-cli system ping
unity-cli raw get_editor_state --json '{}'
unity-cli raw read_console --json '{"count":20}'
unity-cli raw update_project_settings --json '{"confirmChanges":true,"player":{"companyName":"MyStudio"}}'
unity-cli raw profiler_start --json '{}'
unity-cli raw profiler_stop --json '{}'
unity-cli raw package_manager --json '{"action":"install","packageId":"com.unity.inputsystem"}'
```

## Examples

- "Show me the latest Unity console errors."
- "Update the company name in Project Settings."
- "Start the profiler, record briefly, stop, and report the status."

## References

- [runtime-checklist.md](references/runtime-checklist.md): connection and instance prerequisites.
- [editor-ops-checklist.md](references/editor-ops-checklist.md): safer sequence for settings, package, or profiler changes.