scene-unload

Unload an opened scene from the Unity Editor (asynchronously via `SceneManager.UnloadSceneAsync`). Use 'scene-list-opened' to find the scene name first.

Quality

57%

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

Quality

Content

61%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 content is actionable and well-structured with executable CLI examples, but it is held back by redundant input descriptions, missing validation for a destructive operation, and somewhat bulky inlined schemas.

Suggestions

Collapse the redundant `name` descriptions into a single source (keep either the Inputs bullet or the Input table, not both) and reference the JSON schema once.

Add a validation/verification checkpoint (e.g., warn that unloading discards unsaved changes and confirm/suggest saving first, then verify the scene is gone via 'scene-list-opened').

Move the full input/output JSON schemas into a separate reference file (e.g., references/schemas.md) and link to it to keep the overview lean.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable commands, but the `name` parameter is described three times (Inputs bullet, Input table, Input JSON Schema) and the intro repeats the frontmatter description, so it could be tightened.	3 / 5
Actionability	Provides copy-paste ready `unity-mcp-cli run-tool scene-unload` commands covering inline, file, and stdin invocation plus concrete troubleshooting/install commands, with only minor gaps (generic placeholder value).	4 / 5
Workflow Clarity	The single action is unambiguous, but unloading a scene is destructive (discards unsaved state) and there is no validation/verification checkpoint, so workflow clarity is capped at 3 per the rubric.	3 / 5
Progressive Disclosure	Well-organized sections with a clearly signaled one-level reference to the `/unity-initial-setup` skill and no nested references, though the inlined input/output JSON schemas are bulky content that could be split out.	4 / 5
	Total	14 / 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 is specific and clearly distinct, naming the exact Unity API and a prerequisite tool, but it omits any explicit 'when to use' trigger guidance and has only partial natural-keyword coverage.

Suggestions

Add an explicit 'Use when...' trigger clause (e.g., 'Use when the user wants to close or remove an opened scene from the Unity Editor without saving it').

Include a few natural synonyms users might say (e.g., 'close scene', 'remove scene from editor') alongside 'unload'.

Consider mentioning the destructive nature (unsaved changes are discarded) so the trigger guidance signals when caution is warranted.

Dimension	Reasoning	Score
Specificity	Names the domain (Unity Editor scenes) and one concrete action (unload) with the specific API `SceneManager.UnloadSceneAsync`, plus a prerequisite hint, but does not list several actions so it stops at '1-2 concrete actions'.	3 / 5
Completeness	The 'what' is clear (unload an opened scene asynchronously), but there is no 'Use when...' clause or explicit trigger guidance, which caps completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Relevant natural terms appear ('Unload an opened scene', 'Unity Editor', 'scene') but common synonyms/variations are missing and `SceneManager.UnloadSceneAsync` is technical jargon, so coverage is partial.	3 / 5
Distinctiveness Conflict Risk	It targets a clear niche (unloading opened Unity scenes) with distinct triggers and references the sibling 'scene-list-opened' skill, leaving only minor overlap risk with closely related scene skills.	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-unload/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.