| name | unity-skill-generate |
| description | Regenerate every `SKILL.md` from the project's currently-registered MCP tools into the configured skills folder (or a project-relative override path). Writes the YAML `description:` from `[AiSkillDescription]` and the body from `[AiSkillBody]`. |
Skill (Tool) / Generate All
Generate all skills from the existed Tools in the Unity Project.
Inputs
path (optional) — project-relative skills folder (e.g. .claude/skills). Absolute paths and .. traversal segments are rejected. When null/empty, the editor's configured SkillsRootFolderAbsolutePath is used.
Behavior
Creates the destination folder if missing, then invokes McpPluginInstance.GenerateSkillFiles(...) to emit a SKILL.md per registered MCP tool. The plugin's SkillsPath is temporarily swapped to the target folder and restored in finally so the on-disk configuration is unchanged after the call returns.
How to Call
unity-mcp-cli run-system-tool unity-skill-generate --input '{
"path": "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-generate --input-file args.json
Or pipe via stdin (recommended):
unity-mcp-cli run-system-tool unity-skill-generate --input-file - <<'EOF'
{"param": "value"}
EOF
Troubleshooting
If unity-mcp-cli is not found, either install it globally (npm install -g unity-mcp-cli) or use npx unity-mcp-cli instead.
Read the /unity-initial-setup skill for detailed installation instructions.
Input
| Name | Type | Required | Description |
|---|
path | string | No | Path to the skills folder. If null or empty, the default path will be used. |
Input JSON Schema
{
"type": "object",
"properties": {
"path": {
"type": "string"
}
}
}
Output
This tool does not return structured output.