scene-create

Create a new Unity scene asset and save it at the given `.unity` path. Use 'scene-list-opened' to inspect the resulting opened-scene set afterwards.

Quality

60%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./Unity-MCP-Plugin/.claude/skills/scene-create/SKILL.md

Quality

Content

67%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with executable CLI examples and a clear single-step workflow, supported by well-organized sections. Its main weakness is redundancy: parameters are described three times and the input table has empty cells.

Suggestions

Remove the empty "Input" table rows for newSceneSetup/newSceneMode (typed `any` with no description) since the prose "Inputs" section and the JSON schema already cover them.

Consolidate the "Inputs" prose and the "Input JSON Schema" so each parameter is described once, keeping the schema for the enum values.

Add a brief validation checkpoint before saving, e.g. note behavior when the `.unity` path already exists, to strengthen workflow clarity for this potentially overwriting operation.

Dimension	Reasoning	Score
Conciseness	Inputs are restated three times (the "Inputs" prose, an "Input" table whose newSceneSetup/newSceneMode rows are typed `any` with empty descriptions, and the "Input JSON Schema"), which is unnecessary padding that could be tightened; it is otherwise mostly efficient.	3 / 5
Actionability	Concrete, copy-paste-ready bash commands are provided via `unity-mcp-cli run-tool scene-create --input`, plus `--input-file` and stdin pipe alternatives and troubleshooting; the generic `string_value` placeholders are the only minor gap keeping it from 5.	4 / 5
Workflow Clarity	The single action is unambiguous and the body surfaces a post-creation verification step ("Use 'scene-list-opened' tool to list all opened scenes after creation"), but there is no pre-check validation for an existing path, a minor gap versus the explicit-checkpoint anchor at 5.	4 / 5
Progressive Disclosure	Sections are well organized (Inputs, Behavior, How to Call, Troubleshooting, schemas) with only one clearly signaled external reference ("/unity-initial-setup skill") and no nested references; the redundant input sections are the minor organization gap preventing a 5.	4 / 5
	Total	15 / 20 Passed

Description

53%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description clearly conveys what the skill does with a concrete, specific action, but it lacks any explicit "when to use it" trigger guidance, which caps completeness. Keywords are relevant but not comprehensive.

Suggestions

Add a 'Use when...' clause with concrete trigger phrases (e.g., 'Use when creating or initializing a new Unity scene, or when the user asks to add a .unity scene asset').

Broaden natural trigger terms with synonyms and the file extension, e.g. 'new scene', 'add scene', '.unity file', 'Unity scene asset'.

Add one more concrete capability detail (e.g., choosing EmptyScene vs DefaultGameObjects setup) to lift specificity from 3 to 4.

Dimension	Reasoning	Score
Specificity	Quotes "Create a new Unity scene asset and save it at the given `.unity` path" name the domain plus 1-2 concrete actions (create, save); the follow-up inspection is a pointer to another skill rather than an additional capability, so it is not comprehensive enough for a 4.	3 / 5
Completeness	The "what" is clearly stated ("Create a new Unity scene asset and save it"), but there is no "Use when..." clause or equivalent trigger guidance, which per the rubric caps completeness at 3.	3 / 5
Trigger Term Quality	Natural keywords like "Unity scene", "scene asset", and ".unity" are present, but common variations/synonyms and an explicit trigger phrase are missing, fitting the 3 anchor better than the broader 4 anchor.	3 / 5
Distinctiveness Conflict Risk	"Create a new Unity scene asset and save it at the given `.unity` path" carves a clear niche with low conflict risk, though it may overlap slightly with sibling scene skills such as the referenced scene-list-opened, placing it at 4 rather than 5.	4 / 5
	Total	13 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: IvanMurzak/Unity-MCP
Path: Unity-MCP-Plugin/.claude/skills/scene-create/SKILL.md
Commit: 07b8f65

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.