script-delete

Delete one or more `.cs` script files from disk, refresh the AssetDatabase, and wait for Unity compilation to settle before delivering the final result via the request's `requestId`. Pair with 'script-read' to inspect files before deletion.

Quality

62%

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/script-delete/SKILL.md

Quality

Content

57%

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

The body is well-structured and gives concrete CLI guidance, but it suffers from redundant input sections, an incorrect placeholder/type for the `files` array, and no explicit post-deletion verification loop for a destructive batch operation.

Suggestions

Consolidate the duplicate 'Inputs' and 'Input' sections into a single parameter description, and fix the example to show a real array (e.g. `["Assets/Scripts/MyScript.cs"]`) with the table type set to `array` rather than `any`.

Add an explicit verification step in the Behavior/How-to-Call workflow — e.g. confirm each file (and its `.meta`) no longer exists after deletion and before relying on the post-compilation result — to create a validate->delete->verify feedback loop for this destructive batch operation.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete CLI commands and an input schema, but it duplicates the `files` parameter across an 'Inputs' prose section, an 'Input' table, and a JSON schema, and the misleading `"files": "string_value"` placeholder adds noise.	2 / 3
Actionability	Provides executable `unity-mcp-cli run-tool script-delete` commands and an input JSON schema, but the example value `"string_value"` and the table type `any` are incorrect for the array field, undermining copy-paste readiness.	2 / 3
Workflow Clarity	The sequence (validate, delete + sibling .meta, AssetDatabase.Refresh, wait for compilation, deliver via requestId) is present, but for a destructive batch operation there is no explicit verification checkpoint or error-recovery feedback loop, capping this dimension at 2.	2 / 3
Progressive Disclosure	It is a self-contained single-file skill (no references/scripts/assets bundle directories exist) with well-organized sections and no need for external file references, so well-organized sections suffice for a 3.	3 / 3
	Total	9 / 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 distinguishes the skill well, but it lacks an explicit 'Use when...' trigger clause and its natural-language keyword coverage is moderate. Adding a usage-trigger sentence would lift the weaker dimensions.

Suggestions

Add an explicit 'Use when...' clause naming user-facing triggers, e.g. 'Use when the user asks to delete or remove Unity script files (.cs).'

Broaden trigger terms with natural variations like 'remove', 'Unity script', or 'MonoBehaviour file' rather than relying on technical identifiers like 'AssetDatabase' and 'requestId'.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions explicitly: 'Delete one or more `.cs` script files from disk, refresh the AssetDatabase, and wait for Unity compilation to settle before delivering the final result via the request's `requestId`'.	3 / 3
Completeness	The 'what' is clearly stated, but there is no explicit 'Use when...' trigger clause; 'Pair with script-read to inspect files before deletion' is a pairing hint, not a usage trigger, which caps completeness at 2 per the rubric guideline.	2 / 3
Trigger Term Quality	Natural terms like 'Delete', '`.cs` script files', and 'Unity compilation' are present, but coverage lacks common variations ('remove', 'Unity script', 'MonoBehaviour') and leans on technical jargon ('AssetDatabase', 'requestId').	2 / 3
Distinctiveness Conflict Risk	The niche is distinct — deleting Unity `.cs` scripts with AssetDatabase refresh and post-compilation delivery — and the explicit 'script-read' pairing helps separate it from sibling script skills, making accidental triggering unlikely.	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/script-delete/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.