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

66%

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

65%

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

The skill is actionable with a clear executable command, but suffers from redundant input descriptions and inlined verbose schemas. Workflow sequencing and validation checkpoints are implicit rather than explicit.

Suggestions

Remove the duplicated input descriptions — keep either the 'Inputs' prose or the 'Input' table, not both.

Add an explicit validation step: after calling scene-open, check the returned IsValidScene/IsLoaded flags before proceeding.

Move the full input/output JSON schemas into a reference file (e.g. references/schemas.md) and link to it from SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly functional but redundant — the 'Inputs' prose section and the 'Input' table describe sceneRef/loadSceneMode twice, and two full JSON schemas with $defs inflate the token budget; it could be tightened.	2 / 3
Actionability	Provides a concrete, copy-paste-ready CLI invocation ('unity-mcp-cli run-tool scene-open --input ...') plus --input-file and stdin variants, matching the fully-executable anchor.	3 / 3
Workflow Clarity	The find-then-open sequence is only loosely signaled ('Use assets-find to find the scene asset first') with no explicit validation/verification of the returned scene list, so it sits at the 'sequence present but checkpoints missing' anchor.	2 / 3
Progressive Disclosure	Content is organized into sections but is monolithic — the full input/output JSON schemas (well over 50 lines) are inlined in SKILL.md rather than split into reference files, with no bundle files present.	2 / 3
	Total	9 / 12 Passed

Description

67%

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 specific and clearly distinguishable, but lacks an explicit 'Use when' trigger clause, which caps its completeness. Trigger term coverage is adequate rather than comprehensive.

Suggestions

Add an explicit 'Use when...' clause stating when to invoke this skill (e.g. 'Use when the user asks to open or load a Unity scene').

Broaden trigger terms to include natural variations like 'load scene' and 'add scene' alongside 'open scene'.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — 'Open a Unity scene asset in Single or Additive mode', 'Returns the post-open list of all opened scenes', and 'Use assets-find to locate the scene asset first' — matching the multiple-specific-actions anchor.	3 / 3
Completeness	It clearly states what the skill does but has no 'Use when...' clause or equivalent explicit trigger guidance, which per the guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	Natural terms like 'open a Unity scene' and 'scene asset' are present, but coverage is thin and lacks common variations a user might say (e.g. 'load scene', 'add scene'), landing at the 'some relevant keywords but missing variations' anchor.	2 / 3
Distinctiveness Conflict Risk	Opening Unity scenes in Single/Additive mode is a narrow, well-defined niche with distinct triggers unlikely to conflict with other skills.	3 / 3
	Total	10 / 12 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: e0a24ef

Reviewed: about 10 hours 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.