editor-application-get-state

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

Quality

63%

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

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a clean, actionable tool-wrapper page: executable invocation patterns, troubleshooting, and a complete output contract. Its main weaknesses are a duplicated intro sentence, a stray placeholder input parameter, and a large inline schema that limits progressive disclosure.

Suggestions

Remove or tighten the opening paragraph that repeats the frontmatter description to improve conciseness.

Drop the empty `nothing` parameter row/example or document why the tool takes no meaningful input, so the Input section is not noise.

Consider moving the full output JSON schema to a referenced file (e.g. OUTPUT.md) and keeping only a short field summary inline to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient (CLI usage, schemas, troubleshooting), but the opening paragraph restates the description and the input table carries a placeholder `nothing` parameter with an empty description, adding noise that could be trimmed.	2 / 3
Actionability	It gives copy-paste-ready executable commands with inline, file, and stdin variants plus a troubleshooting section, so a caller knows exactly how to invoke the tool.	3 / 3
Workflow Clarity	This is a simple single-action skill whose Behavior section ('Snapshots Editor state via EditorStatsData.FromEditor() on the main thread and returns the result') makes the single action unambiguous, qualifying for 3 under the simple-skills note.	3 / 3
Progressive Disclosure	Sections are well organized and the only external pointer is a one-level skill reference (/unity-initial-setup), but the body is dominated by a large inline output JSON schema that could be split into a reference file; with no bundle files present this is acceptable but not optimal.	2 / 3
	Total	10 / 12 Passed

Description

50%

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 about what state is returned but reads as a technical API caption rather than activation-optimized prose: it lacks a 'Use when...' trigger clause and leans on the internal type name. It is solid but mid-tier on every dimension.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks about Unity Editor play mode, paused state, or whether scripts are compiling.'

Lead with user-natural terms ('Unity Editor state', 'is the editor in play mode') instead of the internal `UnityEditor.EditorApplication` type name.

Clarify the single action as a concrete capability ('Query whether the Unity Editor is playing, paused, or compiling') to nudge specificity toward level 3.

Dimension	Reasoning	Score
Specificity	Names a concrete domain (UnityEditor.EditorApplication state) and enumerates concrete outputs ('playmode, paused state, compilation state, and related flags'), but it is a single action ('Return the current state') rather than multiple distinct actions as the level-3 anchor requires.	2 / 3
Completeness	It clearly answers 'what does this do' but provides no 'Use when...' clause or equivalent explicit trigger guidance, so completeness is capped at 2 per the rubric guideline.	2 / 3
Trigger Term Quality	It includes some natural terms users might say ('playmode', 'paused state', 'compilation state'), but the headline term is the technical API name `UnityEditor.EditorApplication` and it omits common variations like 'Unity editor state' or 'is Unity compiling'.	2 / 3
Distinctiveness Conflict Risk	The Unity EditorApplication niche is fairly specific, but with no explicit trigger terms and a likely family of sibling Unity MCP editor skills, it could still overlap with similar skills.	2 / 3
	Total	8 / 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/editor-application-get-state/SKILL.md
Commit: e0a24ef

Reviewed: about 12 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.