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

74%

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

61%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 a compact, actionable tool doc with executable CLI commands and a clear validation contract. It is weakened by triple-stated input details, a placeholder example that contradicts the array schema, and no error-recovery guidance for a destructive batch operation.

Suggestions

Consolidate the three repetitions of the `files` parameter (## Inputs, ## Input table, and JSON schema block) into one section.

Fix the "How to Call" example to show a real array value (e.g. "files": ["Assets/Scripts/MyScript.cs"]) matching the input schema.

Add brief error-recovery guidance for the destructive batch operation — expected errors when a path is missing or invalid, and what to do if post-delete compilation fails.

Dimension	Reasoning	Score
Conciseness	The `files` parameter is stated three times — in "## Inputs", the "## Input" table, and the full Input JSON Schema block — and the generic CLI invocation boilerplate (input-file/stdin variants) adds padding; this is more than the minor trimming of the 4 anchor.	3 / 5
Actionability	Concrete, executable CLI commands, an input schema, and troubleshooting for a missing binary give mostly copy-paste-ready guidance. It falls short of 5 because the "How to Call" example shows "files": "string_value" while the schema requires an array of strings, so the sample as written would fail.	4 / 5
Workflow Clarity	This is a destructive, batch operation; input validation (non-empty, `.cs` suffix, exists on disk) is described as tool-internal behavior, but there is no feedback loop or error-recovery guidance (what to do when a path is missing, deletion fails, or compilation errors), so the destructive/batch cap holds it at 3.	3 / 5
Progressive Disclosure	With no bundle files and a short body, all content lives appropriately in SKILL.md with no nested references. Minor organization gaps — duplicated Input sections ("## Inputs" vs "## Input") and Troubleshooting nested oddly under "How to Call" — keep it below the 5 anchor.	4 / 5
	Total	14 / 20 Passed

Description

75%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.

A specific, well-scoped description that clearly states concrete actions in third-person voice. Its main weakness is the absence of an explicit 'Use when...' trigger clause and missing natural synonyms like 'remove', which weakens both completeness and trigger coverage.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to delete or remove Unity C# scripts (.cs files) from the project."

Include natural synonyms such as 'remove' and 'clean up scripts' alongside 'delete' to broaden trigger coverage.

Keep the existing concrete action list and requestId/compilation detail — it is specific and distinctive.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions — "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`" — with comprehensive coverage of the tool's behavior, matching the 5 anchor rather than the 4 anchor's 'minor gaps'.	5 / 5
Completeness	The 'what' is clear and concrete, but there is no explicit 'Use when...' trigger clause; the pairing hint "Pair with 'script-read' to inspect files before deletion" only weakly implies when to use it, which caps completeness at 3.	3 / 5
Trigger Term Quality	Good natural keyword coverage including 'Delete', 'script files', 'Unity', '.cs', and 'compilation', but common synonyms a user might say ('remove script', 'delete scripts from the Unity project') are missing, placing it just below the 5 anchor.	4 / 5
Distinctiveness Conflict Risk	A clear niche — Unity `.cs` script deletion with an AssetDatabase refresh and compile-settle/requestId delivery contract — with distinct triggers and minimal overlap risk against generic file-handling skills.	5 / 5
	Total	17 / 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/script-delete/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.