editor-selection-get

Get information about the current Selection in the Unity Editor — active object, active transform, selected GameObjects, transforms, instance IDs, and asset GUIDs (each enrichment is opt-in). Pair with 'editor-selection-set' to change the selection.

Quality

81%

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

Quality

Content

77%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 executable commands and clear parameter semantics, but token efficiency and progressive disclosure suffer from a triple-duplicated input specification and a monolithic inlined output schema. Moving the output schema to a references file and collapsing the input duplication would substantially tighten it.

Suggestions

Move the full output JSON schema into a references/ file (e.g. references/output-schema.md) and keep only a short example response or field summary in SKILL.md.

Collapse the input specification to a single location — the Toggles section already lists all six booleans with defaults; remove the redundant Input table (with empty description cells) and the Input JSON Schema block.

Trim internal schema commentary (priority rankings, default values for edge cases) to only what a caller needs to invoke the tool.

Dimension	Reasoning	Score
Conciseness	The six input booleans are repeated three times (Toggles section, Input table, and Input JSON Schema), making two of the three pure duplication, and the ~150-line output JSON schema is inlined wholesale. Not score 4 because this goes beyond 'minor instances' of over-explanation.	3 / 5
Actionability	Provides a fully executable `unity-mcp-cli run-tool editor-selection-get` command with complete JSON input, plus `--input-file`, stdin heredoc variants, and a concrete troubleshooting fallback (`npm install -g unity-mcp-cli` or `npx`). Copy-paste ready.	5 / 5
Workflow Clarity	A simple single-step tool-invocation skill whose single action is unambiguous: the toggles section explains exactly what each parameter populates, and error recovery for a missing CLI is included. Per the simple-skill exception this earns 5; the skill is read-only so no destructive/batch validation cap applies.	5 / 5
Progressive Disclosure	No bundle files exist, yet roughly 150 lines of raw output JSON schema are inlined directly in SKILL.md — content that clearly belongs in a separate reference file. Structure (section headers) is present, so it sits at anchor 3 rather than 2.	3 / 5
	Total	16 / 20 Passed

Description

75%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.

A specific, well-scoped description with concrete enumerated outputs and good domain keywords, undermined only by the complete absence of a "when to use this" trigger clause. It clearly distinguishes itself from the paired set-selection skill.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks what is selected in the Unity Editor, or wants the active object, transform, instance ID, or asset GUID of the current selection."

Include natural trigger variations users would say, such as "what's selected", "get selected objects", or "selection in the hierarchy/inspector".

Dimension	Reasoning	Score
Specificity	Enumerates concrete capabilities: "active object, active transform, selected GameObjects, transforms, instance IDs, and asset GUIDs", comprehensively covering the tool's output surface rather than stopping at 1-2 actions.	5 / 5
Completeness	The "what" is clear and detailed, but there is no "Use when..." clause or equivalent explicit trigger guidance; "Pair with 'editor-selection-set'" is complementary information, not a trigger, which caps completeness at 3.	3 / 5
Trigger Term Quality	Natural Unity terms are present ("current Selection in the Unity Editor", "selected GameObjects", "asset GUIDs", "instance IDs"), but common phrasings users would say such as "what's selected" or "get the selected objects" are missing.	4 / 5
Distinctiveness Conflict Risk	A clear niche (Unity Editor Selection querying) with explicit disambiguation from its sibling tool ('editor-selection-set' to change the selection); minimal conflict risk with other skills.	5 / 5
	Total	17 / 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/editor-selection-get/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.