# Unity Cli

> >

- **Type:** Skill
- **Install:** `agentstack add skill-niqibiao-unity-cli-skill-unity-cli`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [niqibiao](https://agentstack.voostack.com/s/niqibiao)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** Apache-2.0
- **Upstream author:** [niqibiao](https://github.com/niqibiao)
- **Source:** https://github.com/niqibiao/unity-cli-skill/tree/main/skills/unity-cli

## Install

```sh
agentstack add skill-niqibiao-unity-cli-skill-unity-cli
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# Unity CLI

One CLI (`cs`) drives everything; subcommands cover all operations.
Decision order for any task: **built-in command → snippet → raw exec**.

## Running `cs`

`cs` below = `python "/scripts/cli/cs.py"`, where `` is THIS
skill's base directory (shown when the skill loads — an absolute path). Expand `cs`
to that full command on every call, and always pass `--json`. **Do not pass
`--project`** — the CLI auto-detects the Unity project (it walks up from the working
directory, and from its own committed location). Prefix with
`PYTHONDONTWRITEBYTECODE=1` so running the CLI leaves no `__pycache__` in the project:

```bash
PYTHONDONTWRITEBYTECODE=1 python "/scripts/cli/cs.py" command --json --input req.json
```

No bootstrap/copy step — the CLI runs in place from this skill. First-time use needs the
**Unity package** in the project: `cs setup` installs it (see `references/setup.md`), and
`cs status` reports `NOT FOUND` until Unity resolves it. The first command auto-caches the
resolved package path (machine-local, under your home cache), so an explicit `cs setup` is
a convenience, not a gate.

### Passing parameters — `--input` JSON (never inline)

`command`, `exec`, `batch`, and `complete` take their params as a **single JSON object
written to a file** (or `-` for stdin), never as inline shell arguments. Write the JSON
with your file tool, then pass `--input ` — this removes all shell quoting/escaping
of C# code and nested JSON:

```bash
cs command --json --input req.json    # req.json: {"ns":"gameobject","action":"create","args":{"name":"Cube"}}
cs exec    --json --input req.json    # req.json: {"code":"Debug.Log(\"hi\");"}
cs exec    --json --file snippet.cs   # exec also accepts raw C# from a .cs file
cs batch   --json --input req.json    # req.json: {"commands":[ … ],"stopOnError":true}
```

## Routing — pick the subcommand

| Task | Subcommand | Detail |
|------|------------|--------|
| Structured editor ops (GameObject/component/scene/prefab/asset/material/screenshot/profiler) | `cs command --input` | references/commands.md |
| Raw C# in the live Editor (fallback) | `cs exec` | references/exec-code.md |
| Reusable C# snippet library | `cs snippets …` | references/snippets.md |
| Audit / validate snippets | `cs snippets doctor` / `stats` | references/snippets-audit.md |
| Refresh / recompile after writing .cs | `cs refresh` | references/refresh.md |
| Sync custom-command catalog / maintainer audit | `cs catalog sync` / `cs list-commands` | references/catalog.md |
| Connection / editor status | `cs status` / `cs health` | references/status.md |
| First-time package setup / version-check | `cs setup` | references/setup.md |

## Conventions (all subcommands)

- Always `--json`; the envelope is `{ "ok", "exitCode", "summary", "data" }` — check
  `ok` / `exitCode` for success.
- **Never pass `--project`** — the CLI auto-detects the project. Pass `--project `
  only to deliberately target a different project.
- Prefer `cs command` over `cs exec` when a built-in covers the task; check the snippet
  library (`cs snippets search `) before falling back to ad-hoc `cs exec`.
- A `⚠ version mismatch` warning means the installed Unity package and the CLI are on
  different `major.minor` lines — align them (see references/setup.md). It warns; it
  does not block.
- `--json` and the expanded `python … cs.py …` command line are **agent-internal** —
  for you to run and parse, never to paste to the user. When a step needs the user to
  act (e.g. open Unity to resolve the package) and then re-verify, ask them in plain
  language to **check unity-cli status**; run `cs status` yourself to read the result.

## Source & license

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

- **Author:** [niqibiao](https://github.com/niqibiao)
- **Source:** [niqibiao/unity-cli-skill](https://github.com/niqibiao/unity-cli-skill)
- **License:** Apache-2.0

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

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-niqibiao-unity-cli-skill-unity-cli
- Seller: https://agentstack.voostack.com/s/niqibiao
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.