scene-get-data

Retrieve the list of root GameObjects in the specified opened scene (or the active scene when `openedSceneName` is empty). Supports token-saving path-scoped reads over the root-GameObjects array via `paths` or `viewQuery`. Use 'scene-list-opened' to enumerate scenes.

Quality

72%

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

Quality

Content

77%

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 concrete, copy-paste CLI examples and clear single-tool workflow guidance, but it is weighed down by large inline JSON schemas that duplicate the Input table and could be factored into a reference file.

Suggestions

Move the full input/output JSON schemas into a reference file (e.g. references/schemas.md) and keep only the Input table plus a one-line pointer in SKILL.md to cut the bulk.

Drop field descriptions from the inline schema that merely restate the Input table rows to remove redundancy.

Dimension	Reasoning	Score
Conciseness	The prose is tight and free of concepts Claude already knows, but the ~300 lines of inline input/output JSON schema — much of it duplicating the Input table — add bulk that could be tightened, matching the level-2 anchor of mostly efficient with some excess.	2 / 3
Actionability	"How to Call" gives copy-paste-ready executable commands (`unity-mcp-cli run-tool scene-get-data --input ...`, `--input-file`, stdin pipe) plus concrete install fallbacks and a worked path-syntax example, matching the level-3 anchor.	3 / 3
Workflow Clarity	This is a simple single-action read-only tool whose invocation is unambiguous, and the troubleshooting section covers the main failure mode; per the simple-skills note workflow clarity scores 3 without needing multi-step validation.	3 / 3
Progressive Disclosure	Sections are clearly organized and there are no nested references, but the large inline input/output schemas are content that could live in a separate reference file; with no bundle files present this fits the level-2 anchor of inline content that should be split.	2 / 3
	Total	10 / 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 it lacks an explicit "Use when..." trigger clause and blends natural terms with technical jargon, capping completeness and trigger quality at the mid level.

Suggestions

Add an explicit "Use when..." clause naming the user situations that should trigger this skill (e.g., when the user needs the root GameObjects of an open scene).

Soften or pair technical jargon ("path-scoped reads", "viewQuery") with the plain-language variations a user would actually say (e.g., "read specific fields", "filter scene objects").

Dimension	Reasoning	Score
Specificity	"Retrieve the list of root GameObjects" and "token-saving path-scoped reads over the root-GameObjects array via `paths` or `viewQuery`" name multiple concrete actions rather than vague abstractions, matching the level-3 anchor.	3 / 3
Completeness	The "what" is clearly stated, but there is no explicit "Use when..." trigger; "Use 'scene-list-opened' to enumerate scenes" describes a sibling tool rather than when to invoke this one, so per the guideline completeness caps at 2.	2 / 3
Trigger Term Quality	Natural Unity terms like "scene" and "root GameObjects" appear, but they are mixed with technical jargon ("path-scoped reads", "viewQuery", "Reflector") and miss common variations a user might say, fitting the level-2 anchor rather than full coverage.	2 / 3
Distinctiveness Conflict Risk	The tool has a clear, narrow niche (root GameObjects of a specific opened scene with path-scoped reads) and even points to a distinct sibling tool, making wrong-skill triggering unlikely as in the level-3 anchor.	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-get-data/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.