AgentStack
SKILL verified MIT Self-run

Unity Run

skill-dmitriyyukhanov-claude-plugins-unity-run · by DmitriyYukhanov

Use when running Unity from CLI for any purpose — builds, tests, method execution, asset imports. Handles Unity installation detection, batchmode execution, and log monitoring. Other unity-dev skills depend on this for CLI execution.

No reviews yet
0 installs
5 views
0.0% view→install

Install

$ agentstack add skill-dmitriyyukhanov-claude-plugins-unity-run

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Unity Run? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Run Unity CLI

Execute Unity in batchmode from the command line. This skill handles finding the Unity installation and constructing the CLI command. Calling skills (tests, builds) provide the specific flags.

Step 1: Find the Unity project

Starting from the current working directory, locate ProjectSettings/ProjectVersion.txt by walking up or using Glob. The directory containing ProjectSettings/ is the project root.

If the user provides a project path explicitly, use that instead.

Step 2: Detect Unity installation

Use the plugin's detection script:

UNITY_PATH=$("${CLAUDE_PLUGIN_ROOT}/scripts/find-unity.sh" "")

The script auto-detects Unity via Hub config, default paths, and Hub CLI fallback. It reads the project's ProjectVersion.txt to find the matching editor version.

If detection fails, ask the user to set UNITY_EDITOR_PATH environment variable.

Step 3: Build and run the command

Construct the Unity CLI command with batchmode defaults:

"$UNITY_PATH" -batchmode -projectPath ""  -logFile - -quit

Defaults (always include unless caller overrides):

  • -batchmode — no GUI
  • -projectPath — the detected project root
  • -logFile - — stream log to stdout (use a file path if caller needs to parse logs separately)
  • -quit — exit after execution

Caller provides: the purpose-specific flags (e.g., -runTests, -buildTarget, -executeMethod).

Timeout: Set to 600000ms (10 minutes) by default. Builds may need longer — caller can override.

Step 4: Report results

After execution:

  • Report Unity exit code (0 = success, non-zero = failure)
  • If -logFile - was used, relevant log output is already in stdout
  • If a log file was used, read the last 50 lines on failure for diagnostics

Common flags reference

| Purpose | Flags | |---------|-------| | Run tests | -runTests -testPlatform EditMode -testResults | | Android build | -buildTarget Android -executeMethod | | iOS build | -buildTarget iOS -executeMethod | | Execute method | -executeMethod | | Import assets | -importPackage | | No graphics | -nographics (add for headless servers) |

Platform notes

  • Windows: Unity path uses forward slashes in bash. The detection script handles conversion.
  • PATH inheritance: Unity inherits PATH from its parent process (Unity Hub). After PATH changes, restart Hub + Editor.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.