editor-application-get-state

Return the current state of `UnityEditor.EditorApplication` — playmode, paused state, compilation state, and related flags.

Quality

79%

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

Quality

Content

81%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 — executable CLI commands, troubleshooting, and complete schemas make the tool trivially callable — and the single-step workflow is clear. The weaknesses are token inefficiency: a redundant intro paragraph, generic input-passing boilerplate, and a large inline schema dump that could be split out.

Suggestions

Delete or drastically shorten the opening paragraph, which repeats the frontmatter description almost verbatim.

Trim the generic 'complex input' tip block to one line (or the stdin variant only) since it is boilerplate unrelated to this tool's specific call.

Move the full output JSON schema into a reference file (e.g. references/output-schema.md) and keep a compact field summary in SKILL.md to improve both conciseness and progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The opening paragraph restates the frontmatter description nearly verbatim ('Returns available information about... Such as: playmode, paused state, compilation state, etc.'), and the generic three-variant input-passing boilerplate applies to any tool rather than this one; the empty parameter-description row adds noise. Mostly efficient, but these sections could be tightened — matching anchor 3. Not 4 because the duplicated intro and generic block are more than minor trims.	3 / 5
Actionability	Provides a copy-paste-ready CLI invocation with JSON input, a concrete troubleshooting step for a missing CLI, and complete input/output JSON schemas — fully executable guidance covering the common case. Matches the 'fully executable; copy-paste ready' anchor; no missing key details.	5 / 5
Workflow Clarity	This is a simple, single-task skill (run one command, read the returned state) and the single action is unambiguous, with a feedback step (troubleshooting when the CLI is not found). Per the simple-skill scoring note, a clear single action with error-recovery guidance warrants 5; the operation is read-only so no validation checkpoint is needed.	5 / 5
Progressive Disclosure	Sections are clearly organized (Behavior, How to Call, Troubleshooting, Input, Output) with no nested references and no bundle files. Scored against the actual bundle structure: the ~60-line inline output JSON schema is reference material that could live in a separate file — a minor organization gap matching anchor 4 rather than the fully split structure of anchor 5.	4 / 5
	Total	17 / 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 domain-distinct, cleanly stating what the tool returns with concrete state flags. Its main weakness is the absence of any 'Use when...' trigger guidance, which caps completeness and limits trigger-term coverage.

Suggestions

Add an explicit trigger clause, e.g. 'Use when checking whether the Unity Editor is in Play mode, paused, or compiling scripts.'

Replace the vague 'related flags' with the concrete remaining flags (IsUpdating, editor paths, TimeSinceStartup) to sharpen specificity and distinctiveness.

Include natural user phrasings/synonyms such as 'is Unity compiling' or 'editor play mode state' to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the concrete domain (UnityEditor.EditorApplication) and lists several specific state items — 'playmode, paused state, compilation state, and related flags' — matching the 'several specific actions; minor gaps' anchor. It falls short of 5 only because 'related flags' is unspecific, and exceeds 3 because more than 1-2 concrete items are enumerated.	4 / 5
Completeness	Has a clear 'what' (returns EditorApplication state: playmode, paused, compilation) but no 'Use when...' or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. Not 2 because the 'what' is clear and specific, not vague.	3 / 5
Trigger Term Quality	Includes natural terms users would say — 'current state', 'playmode', 'paused', 'compilation state' — giving good keyword coverage. Not 5: missing common synonyms/phrasings like 'is Unity compiling' or 'is the editor in play mode'; not 3 because the coverage goes beyond bare domain naming.	4 / 5
Distinctiveness Conflict Risk	A clear niche (Unity Editor application state query) with distinct triggers, but 'related flags' is broad and sibling editor-state tools could overlap slightly — matching 'mostly distinct; minor overlap risk'. Not 5 because it does not fully enumerate the flags that distinguish it from adjacent skills.	4 / 5
	Total	15 / 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-application-get-state/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.