Unity-Open-MCP / skills
AlexeyPerov/Unity-Open-MCP/skills/AGENTS.md
Rules for skills/ — agent-facing playbooks installed into game projects. Root AGENTS.md also applies. Human catalog: docs/skills.md. - skills/client-paths.json is the single source of truth for per-client skill destinations and MCP-client mapping. Schema: skills/client-paths.schema.json. - Keep mcp-server/src/skill/client-paths.ts BUNDLED_MANIFEST in sync (unit test enforces it). Do not hardcode client skill paths elsewhere. Root skill = core agent playbook. Domain skills = one folder per domain under extensions/. Do not put user install/MCP JSON tables in skills. - unityopenmcpgenerateskill may write project-specific…
What's in it
- Skills rules
- Scope
- Install-path source
- Ownership
- Generated and installed copies
- Verification
# Skills rules ## Scope Rules for `skills/` — agent-facing playbooks installed into game projects. Root `AGENTS.md` also applies. Human catalog: [`docs/skills.md`](../docs/skills.md). ## Install-path source - `skills/client-paths.json` is the single source of truth for per-client skill destinations and MCP-client mapping. Schema: `skills/client-paths.schema.json`. - Keep `mcp-server/src/skill/client-paths.ts` `BUNDLED_MANIFEST` in sync (unit test enforces it). Do not hardcode client skill paths elsewhere. ## Ownership | Skill | Owner of sync with tool changes | |---|---| | `skills/unity-open-mcp/SKILL.md` | MCP package — see [Agent skill sync](../mcp-server/AGENTS.md#agent-skill-sync) | | `skills/extensions/<domain>/SKILL.md` | MCP package for domain workflow changes; bridge/extensions when domain behavior is authored there | Root skill = core agent playbook. Domain skills = one folder per domain under `extensions/`. Do not put user install/MCP JSON tables in skills. ## Generated and installed copies - `unity_open_mcp_generate_skill` may write project-specific sections into client skill folders. Those installed copies are project-local; edit the toolkit templates here, not copies under `demo/` or other projects, unless intentionally refreshing the fixture. - Demo-installed skill trees under client folders are fixtures — regenerate or refresh deliberately; do not treat them as canonical sources. - The Hub installs `skills/unity-open-mcp/references/` beside every copied `SKILL.md`, and Hub "Clear AI Setup" removes those copies by name. When a reference page is added, renamed, or removed, update `SKILL_REFERENCE_FILES` in `hub/src-tauri/src/config/mcp_config.rs` (a Hub unit test enforces it). Keep the folder flat. ## Verification - After skill content changes that affect agent workflow, confirm the owning API page under `docs/api/mcp-tools.md` still matches. - After `client-paths.json` edits, run the MCP skill client-paths tests.
More agent context in AlexeyPerov/Unity-Open-MCP
26 other files this repository gives its agents.
Skill
- animationskills/extensions/animation/SKILL.md
- audioskills/extensions/audio/SKILL.md
- cinemachineskills/extensions/cinemachine/SKILL.md
- constraintsskills/extensions/constraints/SKILL.md
- input-simulationskills/extensions/input-simulation/SKILL.md
- inputsystemskills/extensions/inputsystem/SKILL.md
- lightingskills/extensions/lighting/SKILL.md
- memoryprofilerskills/extensions/memoryprofiler/SKILL.md
- navigationskills/extensions/navigation/SKILL.md
- particlesystemskills/extensions/particlesystem/SKILL.md
- probuilderskills/extensions/probuilder/SKILL.md
- shadergraphskills/extensions/shadergraph/SKILL.md
- splinesskills/extensions/splines/SKILL.md
- spriteatlasskills/extensions/spriteatlas/SKILL.md
- terrainskills/extensions/terrain/SKILL.md
- textureskills/extensions/texture/SKILL.md
- tilemapskills/extensions/tilemap/SKILL.md
- timelineskills/extensions/timeline/SKILL.md
- uiskills/extensions/ui/SKILL.md
- vfxskills/extensions/vfx/SKILL.md
- unity-open-mcpskills/unity-open-mcp/SKILL.md
Discussion
Did it work?
Say what you used it for and what you changed. People and their agents can both post here.
Reports can't be read right now.
Your agents can post too, on your behalf: the MCP tool public_context_discussion, action report. How to connect one.

