CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

61

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./Unity-MCP-Plugin/.claude/skills/editor-selection-get/SKILL.md
SKILL.md
Quality
Evals
Security

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 call examples and a clear single-action workflow, but it is padded by redundant input listings and a large inline output schema that would benefit from a separate reference file.

Suggestions

Collapse the toggles list, the Input table, and the Input JSON Schema into a single source of truth; remove the empty Description cells.

Move the large Output JSON Schema into a references/ file (e.g. references/output-schema.json) and link to it from the body.

Drop the redundant Input JSON Schema block since the toggles section plus the How-to-Call example already convey the parameters.

DimensionReasoningScore

Conciseness

The how-to-call and toggles sections are lean, but the six boolean params are restated three times (toggles, an Input table with empty description cells, and an Input JSON Schema) and a ~150-line output schema is inlined; could be tightened.

3 / 5

Actionability

Provides a copy-paste ready unity-mcp-cli command with full JSON input plus --input-file and stdin variants and a troubleshooting note, covering the common cases fully.

5 / 5

Workflow Clarity

A single, unambiguous read-only action with no destructive or batch step; the simple-skill exception applies and validation is not required.

5 / 5

Progressive Disclosure

Clear section headers and a well-signaled one-level sibling-skill reference, but no bundle files exist and ~150 lines of output schema are inlined rather than split into a reference file.

3 / 5

Total

16

/

20

Passed

Description

66%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 specific and well-scoped to Unity selection retrieval with good natural trigger terms, but it lacks an explicit 'Use when…' clause, capping completeness. The get/set pairing note gives it solid distinctiveness.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks what is currently selected in the Unity Editor or needs the active object/transform GUIDs.'

Include a couple of natural synonyms such as 'hierarchy selection' or 'selected assets' to broaden trigger coverage.

Make the get vs. set distinction a clearer trigger differentiator rather than only a pairing footnote.

DimensionReasoningScore

Specificity

Enumerates concrete outputs ('active object, active transform, selected GameObjects, transforms, instance IDs, and asset GUIDs') for a single get action; minor coverage gaps keep it just below comprehensive.

4 / 5

Completeness

The 'what' is clear and detailed, but there is no 'Use when…' trigger clause — only a pairing note — so per the missing-trigger guideline completeness is capped at 3.

3 / 5

Trigger Term Quality

Uses natural Unity terms a user would say ('current Selection', 'active object', 'selected GameObjects', 'asset GUIDs'); a few synonyms are missing, so not comprehensive.

4 / 5

Distinctiveness Conflict Risk

A narrow Unity Editor niche with explicit get/set disambiguation ('Pair with editor-selection-set'); mostly distinct with minor overlap risk against the sibling set skill.

4 / 5

Total

15

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
IvanMurzak/Unity-MCP
Reviewed

Table of Contents

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.