$3b
unity-mcp-cli run-system-tool unity-skill-create --input '{
"path": "string_value",
"code": "string_value"
}'
For complex input (multi-line strings, code), save the JSON to a file and use:
unity-mcp-cli run-system-tool unity-skill-create --input-file args.jsonOr pipe via stdin (recommended):
unity-mcp-cli run-system-tool unity-skill-create --input-file - <<'EOF' {"param": "value"} EOF
If unity-mcp-cli is not found, either install it globally () or use instead.
Read the /unity-initial-setup skill for detailed installation instructions.
npm install -g unity-mcp-clinpx unity-mcp-cli| Name | Type | Required | Description |
|---|---|---|---|
path | string | Yes | Path for the C# (.cs) file to be created. Sample: "Assets/Skills/MySkill.cs". |
| CRITICAL — Assembly Definition placement: If the project uses Assembly Definition files (.asmdef), you MUST place the script inside a folder that belongs to an assembly definition which already references all required dependencies (e.g. com.IvanMurzak.McpPlugin, UnityEditor, UnityEngine). Placing the file in the wrong assembly will cause compile errors due to missing type references. Before choosing a path, inspect existing .asmdef files with the assets-find tool to identify the correct assembly folder. | |||
code | string | Yes | C# code for the skill tool. |
{
"type": "object",
"properties": {
"path": {
"type": "string"
},
"code": {
"type": "string"
}
},
"required": [
"path",
"code"
]
}
This tool does not return structured output.