assets-prefab-close

Close the currently opened prefab edit stage. Optionally saves changes back to the prefab asset before closing. Pair with 'assets-prefab-open' to enter the edit mode first.

Quality

78%

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/assets-prefab-close/SKILL.md

Quality

Content

81%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 copy-paste-ready CLI commands, explicit preconditions, error behavior, and the discard-changes consequence of save=false, making the single-action workflow unambiguous. Its main weakness is redundancy: the one-boolean input is documented in three places and the output in two, plus generic CLI boilerplate that could be trimmed.

Suggestions

Consolidate the `save` parameter into a single representation: drop either the "## Inputs" bullet section or the "## Input" table, keeping the JSON Schema only if it adds information beyond the prose.

Trim the generic "For complex input" quote block and Troubleshooting section to a one-line pointer, since they are boilerplate not specific to this tool.

Shorten the Output section by referencing the AssetObjectRef definition once instead of repeating its full description text in both the property and the $defs entry.

Dimension	Reasoning	Score
Conciseness	The single `save` boolean parameter is documented three times ("## Inputs" bullet, "## Input" table, and the Input JSON Schema), and the output is described twice ("## Behavior" and the Output JSON Schema), fitting the 'mostly efficient but includes some unnecessary explanation or could be tightened' anchor. It is below 4 because this duplication is a real redundancy, not just a minor trim.	3 / 5
Actionability	The body provides a fully executable, copy-paste-ready CLI invocation with a concrete example value ("save": false) plus stdin and --input-file variants, and an install fallback (npx unity-mcp-cli), matching the 'fully executable; copy-paste ready code or commands' anchor. It is not 4 because the examples already cover the common cases including error recovery for a missing CLI.	5 / 5
Workflow Clarity	This is a simple single-action skill and the action is unambiguous: it names the prerequisite (open the prefab first with 'assets-prefab-open'), the error condition ("Throws when no prefab stage is currently open"), and the destructive-path consequence ("unsaved changes are discarded when `save` is `false`"). Per the simple-skill exception the single action with explicit validation of preconditions and consequences scores 5.	5 / 5
Progressive Disclosure	Sections are clearly headed and well-organized with no nested references and no orphaned bundle paths (no references/scripts/assets directories exist), fitting the 'good structure; most content appropriately placed; references mostly clear' anchor. It is not 5 because the body exceeds 50 lines and inlines generic CLI-invocation boilerplate and troubleshooting that is not specific to this skill.	4 / 5
	Total	17 / 20 Passed

Description

65%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 communicates a narrow, distinctive capability in Unity prefab editing with concrete verbs, but it lacks an explicit 'Use when...' trigger clause, so the 'when' side of completeness is only implied by the pairing note. Trigger term coverage is good though missing common phrasings like 'exit prefab mode'.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to exit or close prefab editing mode in the Unity Editor, with or without saving changes."

Include natural trigger variations such as "exit prefab mode", "finish editing the prefab", or "discard prefab changes" to strengthen keyword coverage.

State the behavior of both save/discard paths explicitly (e.g. "close and save" vs "close and discard") so both common invocations are named.

Dimension	Reasoning	Score
Specificity	"Close the currently opened prefab edit stage" and "saves changes back to the prefab asset" name the domain plus 1-2 concrete actions, matching the 'names domain and 1-2 concrete actions, but not comprehensive' anchor. It is below 4 because there is no broader list of specific actions, and above 2 because the actions are concrete rather than generic.	3 / 5
Completeness	The 'what' is clearly stated (close the prefab edit stage, optionally saving first), but there is no explicit 'Use when...' clause; "Pair with 'assets-prefab-open' to enter the edit mode first" is a precondition hint rather than trigger guidance, which caps completeness at 3 per the judging guidelines. It is above 2 because the 'what' is concrete and the 'when' is weakly implied.	3 / 5
Trigger Term Quality	Natural terms like "prefab", "prefab edit stage", "close", and "save" back to the "prefab asset" give good keyword coverage, fitting the 'good keyword coverage; a few natural terms missing' anchor. It falls short of 5 because common variations such as "exit prefab mode" or "finish editing prefab" are absent.	4 / 5
Distinctiveness Conflict Risk	"Close the currently opened prefab edit stage" with explicit pairing to 'assets-prefab-open' occupies a clear niche (closing Unity prefab edit mode) with distinct triggers and minimal conflict risk with other skills. No neighboring anchor fits better since the domain is narrowly scoped and unambiguous.	5 / 5
	Total	15 / 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/assets-prefab-close/SKILL.md
Commit: 4c8056f

Reviewed: 8 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.