scene-list-opened

List every scene currently opened in the Unity Editor as a shallow snapshot (name, path, build flags). Use 'scene-get-data' for the deep view of a specific scene.

Quality

71%

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

Quality

Content

85%

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

The body is a tight, actionable tool-wrapper with executable commands and full I/O schemas, well-organized for a simple single-task skill. The only real slack is minor redundancy between the description, the input table, and the input JSON schema.

Dimension	Reasoning	Score
Conciseness	The prose is lean and assumes Claude's competence, but the body repeats the frontmatter description and duplicates the input both as a table and a JSON schema, including an empty-description "nothing" param that adds tokens without value.	2 / 3
Actionability	"unity-mcp-cli run-tool scene-list-opened --input '{...}'" is a complete, copy-paste-ready command, with --input-file and stdin pipe variants and a troubleshooting fallback (npx).	3 / 3
Workflow Clarity	This is a single unambiguous read-only action (call the tool to list opened scenes), which per the simple-skill note earns a 3 with no need for multi-step sequencing or validation.	3 / 3
Progressive Disclosure	No bundle files exist and the content is self-contained, organized into clear labeled sections (Behavior, How to Call, Troubleshooting, Input, Output) with no nested references.	3 / 3
	Total	11 / 12 Passed

Description

57%

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 well-scoped to Unity scene listing with good distinctiveness from the companion scene-get-data skill. Its main gaps are the absence of an explicit trigger clause and limited coverage of natural user phrasings.

Suggestions

Add an explicit "Use when..." clause, e.g. "Use when the user asks which scenes are currently open in the Unity Editor", to raise completeness to 3.

Broaden trigger terms with natural variations users actually say, such as "open scenes", "loaded scenes", or "which scenes are open".

Mention the concrete return shape inline (e.g. "returns one entry per opened scene") to reinforce specificity beyond the single list action.

Dimension	Reasoning	Score
Specificity	"List every scene currently opened in the Unity Editor as a shallow snapshot (name, path, build flags)" names a concrete action with specific output fields, but it is a single action rather than the multiple concrete actions the top anchor calls for.	2 / 3
Completeness	The "what" is clearly stated, but there is no explicit "Use when..." trigger clause, so per the guidelines completeness is capped at 2.	2 / 3
Trigger Term Quality	Natural terms like "scene", "opened", and "Unity Editor" appear, but common variations a user might say ("open scenes", "loaded scenes", "which scenes are open") are missing.	2 / 3
Distinctiveness Conflict Risk	"Use 'scene-get-data' for the deep view of a specific scene" explicitly distinguishes this shallow-listing skill from the deep-view skill, giving it a clear niche.	3 / 3
	Total	9 / 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-list-opened/SKILL.md
Commit: e0a24ef

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