scene-open

Open a Unity scene asset in Single or Additive mode. Returns the post-open list of all opened scenes. Use 'assets-find' to locate the scene asset first.

Quality

58%

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-open/SKILL.md

Quality

Content

58%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 well-structured and actionable with concrete CLI examples, but it is somewhat redundant (input described three ways, full schemas inlined) and lacks a verification step for the state-changing scene-open action.

Suggestions

Add a brief verification step after the call, e.g. check the returned list's IsValidScene / IsLoaded to confirm the scene opened.

De-duplicate the input documentation: keep the table or the JSON schema, not both an Inputs list, a table, and the full schema.

Replace placeholder 'string_value' inputs in the example with realistic values and a note on the AssetObjectRef format.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with clear sections and example commands, but it duplicates the input documentation (an Inputs section, a table, and a full JSON schema all describe sceneRef/loadSceneMode) and embeds large raw JSON schemas that could be trimmed.	3 / 5
Actionability	It provides concrete, copy-paste-ready CLI commands (run-tool with --input, --input-file, stdin pipe) plus troubleshooting for a missing CLI, with only minor gaps such as the placeholder 'string_value' inputs.	4 / 5
Workflow Clarity	Opening a scene is a simple single action, but the workflow omits verification (e.g. confirming the scene opened via the returned list / IsValidScene) and the body lists no validation checkpoint; per rubric, missing validation in a state-changing operation caps workflow clarity at 3.	3 / 5
Progressive Disclosure	Content is well-organized into Inputs, How to Call, Troubleshooting, Input/Output schema sections with no external bundle files to navigate; the main gap is inlining full JSON schemas rather than summarizing them, which keeps it just below 5.	4 / 5
	Total	14 / 20 Passed

Description

57%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 is concrete and specific about what the skill does and points to a prerequisite, but it lacks an explicit 'Use when...' trigger clause and natural trigger phrases, which cap completeness and trigger-term quality.

Suggestions

Add an explicit trigger clause such as 'Use when the user asks to open, load, or switch a Unity scene.'

Include natural synonyms and phrases users actually say, e.g. 'open scene', 'load scene', 'add scene additively'.

Clarify the relationship to 'assets-find' with a brief why (e.g. 'to resolve the scene asset reference') so the trigger condition is self-contained.

Dimension	Reasoning	Score
Specificity	Names the domain and multiple concrete actions ('Open a Unity scene asset in Single or Additive mode', 'Returns the post-open list of all opened scenes') and points to a prerequisite tool, with only minor gaps in coverage.	4 / 5
Completeness	The 'what' is clear (open a scene in a given mode and return opened scenes), but there is no explicit 'Use when...' trigger clause; per the rubric a missing trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	It includes 'Unity scene asset', 'Single or Additive mode', and 'assets-find', but lacks common natural phrases users would say (e.g. 'open scene', 'load scene') and synonyms beyond the mode names.	3 / 5
Distinctiveness Conflict Risk	The skill has a clear niche (opening Unity scenes by mode) distinct from asset-search or scene-editing skills, with only minor overlap risk with closely related scene tools.	4 / 5
	Total	14 / 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-open/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.