assets-create-folder

Create a new folder under a parent folder inside 'Assets/'. The parent path must start with 'Assets/' and every intermediate folder in it must already exist. Refreshes the AssetDatabase at the end and returns the GUID(s) of the created folder(s).

Quality

70%

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

Quality

Content

72%

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 commands and complete schemas, and is well-organized with only one-level references. It loses points for redundant intro/Inputs sections and for lacking an explicit batch error-recovery feedback loop.

Suggestions

Merge the '## Inputs' paragraph, '## Input' table, and '### Input JSON Schema' into a single consolidated input section to remove redundancy.

Add an explicit feedback loop for the batch case, e.g. 'After the call, inspect Errors per entry; fix the offending ParentFolderPath/NewFolderName and re-run only the failed entries.'

Trim the intro paragraph to avoid restating the frontmatter description, and fix the misleading example placeholder (inputs shown as "string_value" when it is an array of objects).

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands and schemas, but the intro paragraph restates the frontmatter description and the '## Inputs', '## Input' table, and '### Input JSON Schema' sections overlap, so it could be tightened; matches the 'mostly efficient but includes some unnecessary explanation' anchor.	2 / 3
Actionability	Provides fully executable CLI commands ('unity-mcp-cli run-tool assets-create-folder --input ...', '--input-file', stdin pipe), troubleshooting, and complete input/output JSON schemas that are copy-paste ready, matching the 'fully executable code/commands' anchor.	3 / 3
Workflow Clarity	The single tool call is unambiguous and validation rules are listed, but this is a batch operation (list of inputs) with no explicit error/retry feedback loop described, so per the batch-operation guideline workflow clarity is capped at 2.	2 / 3
Progressive Disclosure	A single self-contained document with well-organized sections (Inputs, Validation, How to Call, Input, Output) and only a clearly-signaled one-level reference ('Read the /unity-initial-setup skill'), with no deep nesting, matching the 'clear overview with well-signaled one-level-deep references' anchor.	3 / 3
	Total	10 / 12 Passed

Description

67%

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 distinct, naming concrete actions and a clear Unity 'Assets/' niche. Its main weakness is the missing explicit 'Use when...' trigger guidance, which caps completeness, and somewhat technical trigger terms.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to create or organize folders under Assets/ in a Unity project.'

Include more natural user-facing terms ('new folder', 'organize assets', 'subfolder') alongside the technical AssetDatabase/GUID references.

Lead with the most common phrasing a user would say ('Create new folders under Assets/') before the precondition details.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Create a new folder under a parent folder inside Assets/', 'Refreshes the AssetDatabase at the end', 'returns the GUID(s) of the created folder(s)' — matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Clearly answers 'what' the skill does but provides no 'Use when...' clause or equivalent explicit trigger guidance for 'when' to use it, so per the guidelines completeness is capped at 2.	2 / 3
Trigger Term Quality	Contains some natural terms a user would say ('Create a new folder', 'Assets/', 'folder') but leans on technical jargon ('AssetDatabase', 'GUID') and misses common variations like 'new folder' or 'organize assets', matching the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	Targets a clear, narrow niche — creating folders under 'Assets/' in Unity with AssetDatabase/GUID specifics — making it unlikely to trigger for unrelated skills, matching the 'clear niche with distinct triggers' anchor.	3 / 3
	Total	10 / 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/assets-create-folder/SKILL.md
Commit: eb063cf

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