UN

unity-editor-toolkit

Control the Unity Editor programmatically using a WebSocket-based toolkit with 500+ commands.

Install

mkdir -p .claude/skills/unity-editor-toolkit && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/228" && unzip -o skill.zip -d .claude/skills/unity-editor-toolkit && rm skill.zip

Installs to .claude/skills/unity-editor-toolkit

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Automate and control Unity Editor with 500+ commands, real-time WebSocket communication, and SQLite integration for efficient game development.
143 chars · catalog descriptionno explicit “when” trigger
Advanced

Key capabilities

  • Execute 500+ editor commands via JSON-RPC
  • Synchronize GameObjects with SQLite persistence
  • Perform batch operations on 500+ objects
  • Enable multi-scene synchronization
  • Run build pipelines remotely

How it works

Maintains a bidirectional WebSocket connection to send JSON-RPC requests directly to the Unity Editor instance.

Inputs & outputs

You give it
JSON-RPC command
You get back
Editor status or data confirmation

When to use unity-editor-toolkit

  • Automate Unity scene management
  • Programmatically manipulate game objects
  • Run build pipelines remotely
  • Integrate SQLite for persistent asset data

About this skill

Purpose

Unity Editor Toolkit enables comprehensive Unity Editor automation and control from Claude Code. It provides:

  • Extensive Command Coverage: 500+ commands spanning 25 Unity Editor categories
  • Real-time Communication: Instant bidirectional WebSocket connection (JSON-RPC 2.0)
  • SQLite Database Integration: Real-time GameObject synchronization with GUID-based persistence
    • GUID-based Identification: Persistent GameObject tracking across Unity sessions
    • Multi-scene Support: Synchronize all loaded scenes simultaneously (1s interval)
    • Command Pattern: Undo/Redo support for database operations
    • Auto Migration: Automatic schema migration system
    • Batch Operations: Efficient bulk inserts, updates, and deletes (500 objects/batch)
  • Menu Execution: Run Unity Editor menu items programmatically (Window, Assets, Edit, GameObject menus)
  • ScriptableObject Management: Complete CRUD operations with array/list support and all field types
    • Array/List Operations: Add, remove, get, clear elements with nested access (items[0].name)
    • All Field Types: Integer, Float, String, Boolean, Vector*, Color, Quaternion, Bounds, AnimationCurve, ObjectReference, and more
    • Nested Property Traversal: Access deeply nested fields with dot notation and array indices
  • Deep Editor Integration: GameObject/hierarchy, transforms, components, scenes, materials, prefabs, animation, physics, lighting, build pipeline, and more
  • Security First: Multi-layer defense against injection attacks (SQL, command, JSON, path traversal) and unauthorized access
  • Production Ready: Cross-platform support with robust error handling and logging

Always run scripts with --help first to see usage. DO NOT read the source until you try running the script first and find that a customized solution is abslutely necessary. These scripts can be very large and thus pollute your context window. They exist to be called directly as black-box scripts rather than ingested into your context window.


📚 문서 우선 원칙 (필수)

⚠️ CRITICAL: Unity Editor Toolkit skill을 사용할 때는 반드시 다음 순서를 따르세요:

1️⃣ Reference 문서 확인 (필수)

명령어를 사용하기 전에 반드시 skills/references/ 폴더의 해당 문서를 읽으세요:

2️⃣ --help 실행

# 모든 명령어 확인
cd <unity-project-root> && node .unity-websocket/uw --help

# 특정 명령어의 옵션 확인
cd <unity-project-root> && node .unity-websocket/uw <command> --help

3️⃣ 예제 실행

reference 문서의 Examples 섹션을 참고하여 명령어를 실행하세요.

4️⃣ 소스 코드 읽기 (최후의 수단)

  • reference 문서와 --help만으로는 해결 안 될 때만 소스 코드를 읽으세요
  • 소스 코드는 컨텍스트 윈도우를 많이 차지하므로 가능하면 피하세요

이 순서를 무시하면:

  • ❌ 명령어 사용법을 잘못 이해할 수 있음
  • ❌ 옵션을 놓쳐서 원하지 않는 결과가 나올 수 있음
  • ❌ 컨텍스트 윈도우를 낭비할 수 있음

When to Use

Use Unity Editor Toolkit when you need to:

  1. Automate Unity Editor Tasks

    • Create and manipulate GameObjects, components, and hierarchies
    • Configure scenes, materials, and rendering settings
    • Control animation, physics, and particle systems
    • Manage assets, prefabs, and build pipelines
  2. Real-time Unity Testing

    • Monitor console logs and errors during development
    • Query GameObject states and component properties
    • Test scene configurations and gameplay logic
    • Debug rendering, physics, or animation issues
  3. Batch Operations

    • Create multiple GameObjects with specific configurations
    • Apply material/shader changes across multiple objects
    • Setup scene hierarchies from specifications
    • Automate repetitive Editor tasks
  4. Menu and Editor Automation

    • Execute Unity Editor menu items programmatically (menu run "Window/General/Console")
    • Open editor windows and tools via command line
    • Automate asset refresh, reimport, and build operations
    • Query available menu items with wildcard filtering
  5. ScriptableObject Management

    • Create and configure ScriptableObject assets programmatically
    • Read and modify all field types (Vector, Color, Quaternion, AnimationCurve, etc.)
    • Manipulate arrays/lists with full CRUD operations
    • Access nested properties with array index notation (items[0].stats.health)
    • Query ScriptableObject types and inspect asset metadata
  6. Database-Driven Workflows

    • Persistent GameObject tracking across Unity sessions with GUID-based identification
    • Real-time synchronization of all loaded scenes to SQLite database
    • Analytics and querying of GameObject hierarchies and properties
    • Undo/Redo support for database operations via Command Pattern
    • Efficient batch operations (500 objects/batch) for large scene management
  7. CI/CD Integration

    • Automated builds with platform-specific settings
    • Test Runner integration for unit/integration tests
    • Asset validation and integrity checks
    • Build pipeline automation

Prerequisites

Unity Project Setup

  1. Install Unity Editor Toolkit Server Package

    • Via Unity Package Manager (Git URL or local path)
    • Requires Unity 2020.3 or higher
    • Package location: skills/assets/unity-package
  2. Configure WebSocket Server

    • Open Unity menu: Tools > Unity Editor Toolkit > Server Window
    • Plugin scripts path auto-detected from ~/.claude/plugins/...
    • Click "Install CLI" to build WebSocket server (one-time setup)
    • Server starts automatically when Unity Editor opens
  3. Database Setup (Optional)

    • In the Server window, switch to "Database" tab
    • Click "Connect" to initialize SQLite database
    • Database file location: {ProjectRoot}/.unity-websocket/unity-editor.db
    • Click "Start Sync" to enable real-time GameObject synchronization (1s interval)
    • GUID Components: GameObjects are automatically tagged with persistent GUIDs
    • Multi-scene: All loaded scenes are synchronized automatically
    • Analytics: View sync stats, database health, and Undo/Redo history
  4. Server Status

    • Port: Auto-assigned from range 9500-9600
    • Status file: {ProjectRoot}/.unity-websocket/server-status.json
    • CLI automatically detects correct port from this file
  5. Dependencies

    • websocket-sharp (install via package installation scripts)
    • Newtonsoft.Json (Unity's built-in version)
    • Cysharp.UniTask (for async/await database operations)
    • SQLite-net (embedded SQLite database)

Claude Code Plugin

The Unity Editor Toolkit plugin provides CLI commands for Unity Editor control.

Core Workflow

1. Connection

Unity Editor Toolkit CLI automatically:

  • Detects Unity project via .unity-websocket/server-status.json
  • Reads port information from status file (9500-9600 range)
  • Connects to WebSocket server if Unity Editor is running

2. Execute Commands

⚠️ Before executing ANY command, check the reference documentation for your command category (see "📚 문서 우선 원칙" section above).

Unity Editor Toolkit provides 86+ commands across 15 categories. All commands run from the Unity project root:

cd <unity-project-root> && node .unity-websocket/uw <command> [options]

Available Categories (Implemented):

#CategoryCommandsReference
1Connection & Status1COMMANDS_CONNECTION_STATUS.md
2GameObject & Hierarchy8COMMANDS_GAMEOBJECT_HIERARCHY.md
3Transform4COMMANDS_TRANSFORM.md
4Component10COMMANDS_COMPONENT.md
5Scene Management7COMMANDS_SCENE.md
6Asset Database & Editor3COMMANDS_EDITOR.md
7Console & Logging2COMMANDS_CONSOLE.md
8EditorPrefs Management6COMMANDS_PREFS.md
9Wait Commands4COMMANDS_WAIT.md
10Chain Commands2COMMANDS_CHAIN.md
11Menu Execution2COMMANDS_MENU.md
12Asset Management9COMMANDS_ASSET.md
13Prefab12COMMANDS_PREFAB.md
14Material9COMMANDS_MATERIAL.md
15Shader7COMMANDS_SHADER.md

Usage:

cd <unity-project-root> && node .unity-websocket/uw <command> [options]

Required: Check Documentation

# 1. 먼저 명령어 카테고리의 reference 문서를 읽으세요
# 예: Component 명령어 사용 → skills/references/COMMANDS_COMPONENT.md 읽기

# 2. --help로 명령어 옵션 확인
cd <unity-project-root> && node .unity-websocket/uw --help
cd <unity-project-root> && node .unity-websocket/uw <command> --help

# 3. reference 문서의 예제를 참고하여 실행

📖 Complete Documentation by Category

Required Reading: Before using any command, read the Category-specific reference document:

  • 🔴 MUST READ FIRST - COMMANDS.md - Overview and command ro

Content truncated.

When not to use it

  • Running code on hardware devices
  • Editing source files directly outside the Unity Editor

Prerequisites

Unity EditorWebSocket server enabled on port 9500-9600

Limitations

  • Limited to localhost connections
  • Requires specific editor port configuration

How it compares

It provides programmatic remote control over the Editor environment instead of manual inspector interaction.

Compared to similar skills

unity-editor-toolkit side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
unity-editor-toolkit (this skill)106moReviewAdvanced
bullmq-specialist256moNo flagsIntermediate
sqlite-inspector59moReviewIntermediate
write-script-duckdb33moNo flagsIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

bullmq-specialist

davila7

BullMQ expert for Redis-backed job queues, background processing, and reliable async execution in Node.js/TypeScript applications. Use when: bullmq, bull queue, redis queue, background job, job queue.

2595

sqlite-inspector

mikopbx

Проверка консистентности данных в SQLite баз данных MikoPBX после операций REST API. Использовать при валидации результатов API, отладке проблем с данными, проверке связей внешних ключей или инспектировании CDR записей для тестирования.

568

write-script-duckdb

windmill-labs

MUST use when writing DuckDB queries.

321

azure-resource-manager-mysql-dotnet

microsoft

Azure MySQL Flexible Server SDK for .NET. Database management for MySQL Flexible Server deployments. Use for creating servers, databases, firewall rules, configurations, backups, and high availability. Triggers: "MySQL", "MySqlFlexibleServer", "MySQL Flexible Server", "Azure Database for MySQL", "MySQL database management", "MySQL firewall", "MySQL backup".

14

linear-data-handling

jeremylongshore

Data synchronization, backup, and consistency patterns for Linear. Use when implementing data sync, creating backups, or ensuring data consistency across systems. Trigger with phrases like "linear data sync", "backup linear", "linear data consistency", "sync linear issues", "linear data export".

14

local-cluster-manager

multigres

Manage local multigres cluster components (multipooler, pgctld, multiorch, multigateway) - start/stop services, view logs, connect with psql, test S3 backups locally

22

Search skills

Search the agent skills registry