unity-project
Skill7 starsChanged 7 months agoMITView on GitHub
Use when users want to get project settings, quality settings, or shader lists.
In this repository34 other files it gives its agents.
- unity-mcp-skillsSkill
- unity-animatorSkill
- unity-assetSkill
- unity-cameraSkill
- unity-cinemachineSkill
- unity-cleanerSkill
- unity-componentSkill
- unity-consoleSkill
- unity-editorSkill
- unity-eventSkill
- unity-gameobjectSkill
- unity-importerSkill
- unity-lightSkill
- unity-materialSkill
- unity-navmeshSkill
- unity-optimizationSkill
- unity-packageSkill
- unity-perceptionSkill
- unity-physicsSkill
- unity-prefabSkill
- unity-probuilderSkill
- unity-sceneSkill
- unity-scriptableobjectSkill
- unity-scriptSkill
- unity-shaderSkill
- unity-smartSkill
- unity-terrainSkill
- unity-testSkill
- unity-timelineSkill
- unity-toolingSkill
- unity-uiSkill
- unity-uitoolkitSkill
- unity-validationSkill
- unity-xrSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 74
Add a custom Tag.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Project Skills
Overview
Project information and configuration.
Common Mistakes
DO NOT (common hallucinations):
project_savedoes not exist → usescene_save(scene module) oreditor_execute_menumenuPath="File/Save"project_settingsdoes not exist → use specific skills:project_get_render_pipeline,project_get_build_settings, etc.project_set_resolution/project_set_player_settingsdo not exist → Player Settings are read-only viaproject_get_player_settings; to edit, open Project Settings viaeditor_execute_menuwithEdit/Project Settings...project_createdoes not exist → projects are created via Unity Hub, not REST API
Routing:
- For Layer/Tag management →
project_add_tag(this module); Layers are read-only viaproject_get_layers(edit viaeditor_execute_menu→Edit/Project Settings...) - For build settings →
project_get_build_settings(read-only; useeditor_execute_menu→File/Build Settings...to edit)
Skills
project_get_info
Get project information including render pipeline, Unity version, and settings. Parameters: None.
project_get_render_pipeline
Get current render pipeline type and recommended shaders. Parameters: None.
project_list_shaders
List all available shaders in the project. Parameters:
filter(string, optional): Filter by name.limit(int, optional): Max results (default 50).
project_get_quality_settings
Get current quality settings. Parameters: None.
project_get_build_settings
Get build settings (platform, scenes).
Parameters: None.
Returns: { success, activeBuildTarget, buildTargetGroup, sceneCount, scenes }
project_get_packages
List installed UPM packages.
Parameters: None.
Returns: { success, manifest }
project_get_layers
Get all Layer definitions.
Parameters: None.
Returns: { success, count, layers }
project_get_tags
Get all Tag definitions.
Parameters: None.
Returns: { success, count, tags }
project_add_tag
Add a custom Tag.
| Parameter | Type | Required | Default | Description |
| tagName | string | Yes | - | The tag name to add |
Returns: { success, tag }
project_get_player_settings
Get Player Settings.
Parameters: None.
Returns: { success, productName, companyName, bundleVersion, defaultScreenWidth, defaultScreenHeight, fullscreen, apiCompatibility, scriptingBackend }
project_set_quality_level
Switch quality level by index or name.
| Parameter | Type | Required | Default | Description |
| level | int | No | -1 | Quality level index |
| levelName | string | No | null | Quality level name |
Returns: { success, level, name }
Recipe path rule: ../../recipes/project/<command>.md
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

