assets-copy

Copy assets at given paths and store them at new paths. Refreshes the AssetDatabase at the end. Use 'assets-find' to locate the source assets first.

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

Quality

Content

50%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 skill body is actionable with executable CLI examples and troubleshooting, but it is padded with redundant input representations and a full generated output schema. It also lacks an explicit verification checkpoint for what is a batch operation with per-pair error accumulation.

Suggestions

Consolidate the three input representations (bullets, table, JSON schema) into one, and move the full Output JSON Schema into a reference file, keeping only the key response fields (CopiedAssets, Errors) inline.

Add an explicit validation step after the copy, e.g. "Check the Errors list in the response; non-empty means those pairs failed and should be reported or retried."

Fix the example call to show the actual array types, e.g. {"sourcePaths": ["Assets/a.mat"], "destinationPaths": ["Assets/b.mat"]}, so it is copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The inputs are stated three times ("## Inputs" bullets, "## Input" table, and the full Input JSON Schema) and the ~70-line generated Output JSON Schema is inlined wholesale. This is noticeably redundant padding, matching anchor 2 rather than 3, though it never explains concepts Claude already knows.	2 / 5
Actionability	The "## How to Call" section gives concrete, executable unity-mcp-cli commands including the --input-file and stdin heredoc variants, plus troubleshooting for a missing CLI. Minor gap: the example uses "string_value" placeholders where the schema requires arrays of strings, keeping it below anchor 5.	4 / 5
Workflow Clarity	The copy behavior and error-accumulation semantics are stated, but this is a batch operation with no explicit post-copy verification step (e.g., inspecting the Errors list or CopiedAssets in the response). The rubric's batch-operation cap limits workflow clarity to 3 despite the otherwise clear sequence.	3 / 5
Progressive Disclosure	Sections are clearly headed and there are no broken references, but at ~155 lines the bulk of the body is machine-generated schemas that could live in a reference file, and there is no quick-start/overview separation. This fits anchor 3: some structure, but content that should be separate is inline.	3 / 5
	Total	12 / 20 Passed

Description

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

The description is concrete and action-oriented with a clear scope, but it lacks an explicit 'use when' trigger clause and natural-language synonyms that would help users surface it. It communicates what the tool does effectively within its niche.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to copy, duplicate, or move Unity assets to new paths."

Include natural synonyms users might say (duplicate, clone, move) to improve trigger term coverage.

State the batch nature (parallel source/destination lists) in the description so callers know it handles multiple assets at once.

Dimension	Reasoning	Score
Specificity	"Copy assets at given paths and store them at new paths. Refreshes the AssetDatabase at the end" lists several concrete actions (copy, store, refresh, locate via 'assets-find') with only minor coverage gaps. Not 5 because the action list is thin for a single narrow tool rather than comprehensively descriptive.	4 / 5
Completeness	The 'what' is clear (copy assets, refresh AssetDatabase), but there is no explicit 'use when' clause — "Use 'assets-find' to locate the source assets first" is workflow chaining, not a trigger condition. Per the rubric guideline, a missing 'Use when...' caps completeness at 3.	3 / 5
Trigger Term Quality	Relevant keywords exist ("copy assets", "AssetDatabase", "locate the source assets") but common natural variations like "duplicate", "move", or "clone" assets are missing. It matches anchor 3 rather than 4 because synonym coverage is absent.	3 / 5
Distinctiveness Conflict Risk	The Unity asset-copy niche ("Copy assets… Refreshes the AssetDatabase") is mostly distinct with clear tool-family triggers, with only minor overlap risk against sibling skills like assets-move or assets-find. It lacks the fully explicit trigger phrasing of anchor 5.	4 / 5
	Total	14 / 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/assets-copy/SKILL.md
Commit: 4c8056f

Reviewed: 8 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.