scene-create

Create a new Unity scene asset and save it at the given `.unity` path. Use 'scene-list-opened' to inspect the resulting opened-scene set afterwards.

Quality

71%

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/scene-create/SKILL.md

Quality

Content

85%

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 and clearly organized for a single-purpose tool, with executable CLI examples. The main weakness is redundant input presentation and some verbose schema descriptions.

Suggestions

Collapse the three input presentations (Inputs prose, Input table, JSON schema) into one canonical form to reduce token cost.

Trim output-schema field descriptions that restate well-known Unity semantics (e.g., IsValidScene, instanceID) to the minimum needed.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with executable examples, but inputs are presented three times (Inputs prose, Input table, JSON schema) and several output-schema field descriptions restate Unity concepts Claude already knows.	2 / 3
Actionability	Provides fully executable `unity-mcp-cli run-tool scene-create` commands including stdin-pipe and --input-file variants, plus concrete enum values and troubleshooting, all copy-paste ready.	3 / 3
Workflow Clarity	This is a single-action tool whose action is unambiguous (call NewScene + SaveScene, return SceneDataShallow); per the simple-skills note, a clear single action scores 3.	3 / 3
Progressive Disclosure	No bundle files exist; the skill is a self-contained, well-sectioned tool reference (Inputs, Behavior, How to Call, schemas) with no nested references and easy navigation.	3 / 3
	Total	11 / 12 Passed

Description

57%

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 concrete and distinctive but lacks explicit trigger guidance, capping completeness. Trigger terms are present but somewhat technical.

Suggestions

Add a 'Use when...' clause stating when to invoke this skill (e.g., 'Use when the user asks to create a new Unity scene or add a scene asset').

Include more natural user phrasings such as 'new scene' or 'add a scene' alongside the technical 'scene asset' terminology.

Dimension	Reasoning	Score
Specificity	Names concrete actions ('Create a new Unity scene asset and save it at the given `.unity` path') but the scope is a single narrow operation rather than a comprehensive set of capabilities, matching the 'names domain and some actions' anchor.	2 / 3
Completeness	Clearly states what the skill does (create + save a scene) but provides no explicit 'Use when...' trigger clause, so completeness is capped at 2 per the judging guidelines.	2 / 3
Trigger Term Quality	Includes relevant terms ('scene', 'create', '`.unity`', 'opened-scene') but leans on technical phrasing like 'scene asset' and 'opened-scene set' and misses common user variations like 'new scene'.	2 / 3
Distinctiveness Conflict Risk	Scoped to creating Unity scenes at a specific `.unity` path, a clear niche with distinct triggers unlikely to fire for unrelated skills.	3 / 3
	Total	9 / 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/scene-create/SKILL.md
Commit: e0a24ef

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