editor-selection-set

Set the current Selection in the Unity Editor to the provided objects. All `ObjectRef`s must resolve to existing Unity objects; otherwise the call throws. Use 'editor-selection-get' to inspect the current selection first.

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/editor-selection-set/SKILL.md

Quality

Content

42%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 documents a simple tool call with useful behavioral detail (FindObject resolution, RepaintAllViews, returned SelectionData), but it is padded with triple-duplicated input specs, an internally inconsistent example, and ~180 lines of inlined schema that belong in reference files. Fixing the example payload and deduplicating the input documentation would substantially improve it.

Suggestions

Fix the 'How to Call' example to match the schema, e.g. --input '{"select": [{"instanceID": 12345}]}' — the current '"select": "string_value"' placeholder is wrong and misleading.

Deduplicate the input documentation: keep one source of truth (either the concise Inputs section or the schema) instead of restating `select` in prose, an Input table, and a JSON schema; fill in the empty Description cell of the Input table.

Move the large Input/Output JSON schemas into a references/ bundle file (e.g. references/schema.md) and keep only a short summary plus one worked example in SKILL.md.

Dimension	Reasoning	Score
Conciseness	The `select` parameter is specified three times (the prose Inputs section, an Input table whose description cell is empty, and the full Input JSON Schema), and roughly 140 lines of output schema plus generic CLI boilerplate are inlined. This is noticeably verbose with redundant/padded sections, matching anchor 2 rather than the mostly-efficient anchor 3.	2 / 5
Actionability	A concrete CLI invocation is provided, but the example payload '"select": "string_value"' contradicts the documented array-of-ObjectRef shape, so it is not copy-paste executable and the actual call format must be reconstructed from the schema. Fits 'some concrete guidance but incomplete / missing key details' rather than level 4's mostly-executable guidance.	3 / 5
Workflow Clarity	The single-step workflow is present (inspect via editor-selection-get, set, receive post-change SelectionData), but the contradictory example, the 'type: any' input table row, and the empty description cell leave the exact input sequence implicit with no validation checkpoint on the returned snapshot. Anchor 3 (sequence present, checkpoints missing or implicit) fits; level 4 would require an unambiguous, consistent input presentation.	3 / 5
Progressive Disclosure	Section headers give the body some structure, but no bundle files exist (no references/ or scripts/ directories), and the large input/output JSON schemas — bulk reference material — are inlined directly in SKILL.md. This matches 'some structure but content that should be separate is inline'; level 4 would move the schema bulk into referenced files.	3 / 5
	Total	11 / 20 Passed

Description

57%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 states a clear, narrow capability with a useful failure precondition and good distinctiveness, but it never tells Claude when to invoke it — the only guidance is a companion-tool sequencing tip. Adding an explicit trigger clause (e.g. 'Use when the user asks to select, change, or set the current selection/active object in the Unity Editor') would lift completeness and trigger-term quality.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to change, set, or update the current selection or active object in the Unity Editor.'

Include natural user phrasings/synonyms such as 'select', 'highlight', or 'active object' to improve trigger-term coverage.

Optionally mention the returned snapshot (post-change SelectionData) as a second concrete capability so users know the call is verifiable.

Dimension	Reasoning	Score
Specificity	One concrete action ('Set the current Selection in the Unity Editor to the provided objects') plus a stated failure precondition ('All `ObjectRef`s must resolve to existing Unity objects; otherwise the call throws'). This matches the anchor for naming a domain with 1-2 concrete actions, not the level above, which requires several distinct specific actions.	3 / 5
Completeness	The 'what' is clear and specific, but there is no 'Use when...' trigger clause; the closest is a companion-tool pointer ('Use editor-selection-get to inspect the current selection first'), which is usage sequencing rather than a trigger for when this skill is needed. Per the guideline, a missing explicit trigger caps completeness at 3.	3 / 5
Trigger Term Quality	Relevant keywords are present ('Selection', 'Unity Editor', 'objects') but natural user variations are missing (e.g. 'select objects in Unity', 'highlight', 'Hierarchy'). Fits the 'some relevant keywords but missing common variations or synonyms' anchor rather than level 4's 'good keyword coverage'.	3 / 5
Distinctiveness Conflict Risk	Clear niche: mutating the Unity Editor's Selection via a specific tool, explicitly distinguished from its sibling 'editor-selection-get'. Distinct triggers ('Selection', 'Unity Editor') and minimal overlap with unrelated skills, matching the top anchor.	5 / 5
	Total	14 / 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-set/SKILL.md
Commit: 4c8056f

Reviewed: 9 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.