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

60%

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

67%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 provides fully executable invocation examples plus complete schemas for a simple read-only tool. It loses points mainly to a redundant restated description and three over-detailed input-feeding variants for a parameterless call.

Suggestions

Remove the verbatim repeat of the frontmatter description in the opening paragraph to save tokens.

Collapse the three input-feeding variants (inline/file/stdin) into a brief note, since this tool effectively takes no meaningful input.

Consider moving the large output JSON schema to a separate reference file and keeping only key fields inline.

Dimension	Reasoning	Score
Conciseness	The body re-states the description verbatim in the opening line and presents three invocation variants (inline, file, stdin) for a tool that takes no real input, so it is mostly efficient but could be tightened.	3 / 5
Actionability	Concrete, copy-paste-ready bash commands (`unity-mcp-cli run-tool scene-list-opened ...`) plus full input/output JSON schemas give executable guidance, with only the odd placeholder `nothing` parameter as a minor gap.	4 / 5
Workflow Clarity	This is a simple read-only single action that is unambiguous (call the tool, receive the array); the Behavior section explains the mapping, and no validation checkpoint is required for a non-destructive read.	4 / 5
Progressive Disclosure	Content is organized into clearly labeled sections (Behavior, How to Call, Input, Output) with no nested references; the inlined full output JSON schema is bulky reference material that keeps it just short of a 5.	4 / 5
	Total	15 / 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 concrete, third-person, and clearly distinguishes its shallow-snapshot purpose from the related deep-view tool. Its main weakness is the absence of an explicit "Use when..." trigger clause, which limits completeness and trigger-term quality.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks which scenes are currently open/loaded in the Unity Editor."

Include natural synonyms such as "open scenes", "active scenes", or "loaded scenes" to broaden trigger coverage.

Optionally note a complementary second action (e.g. "returns build flags") to push specificity toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	"List every scene currently opened in the Unity Editor as a shallow snapshot (name, path, build flags)" names the domain and one concrete action with specific output fields, but offers only a single action rather than comprehensive coverage.	3 / 5
Completeness	The "what" is clearly stated (list opened scenes as a shallow snapshot), but there is no "Use when..." clause or equivalent explicit trigger guidance, capping completeness at 3.	3 / 5
Trigger Term Quality	"scene", "opened", and "Unity Editor" are relevant natural keywords, but common variations a user might say (e.g. "open scenes", "active scenes", "loaded scenes") are absent.	3 / 5
Distinctiveness Conflict Risk	"List every scene currently opened in the Unity Editor" carves a clear niche and explicitly differentiates from "scene-get-data" for the deep view, leaving only minor overlap risk with sibling Unity 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-list-opened/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.