assets-modify

Modify an asset file in the project. Use 'assets-get-data' first to inspect the asset structure before modifying. Not allowed to modify asset files in the 'Packages/' folder — modify them in 'Assets/'. Three modification surfaces are available (content, pathPatches, jsonPatch) — see the skill body for details.

Quality

61%

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

Quality

Content

57%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 actionable and gives a concrete CLI invocation with variants, but it inlines bulky JSON schemas that belong in a reference file and lacks the validation checkpoint expected of a destructive asset-modification skill. Workflow clarity is capped by the missing verify step.

Suggestions

Add a post-modification verification step (e.g. re-run assets-get-data to confirm the change) to establish a validate -> fix -> retry loop.

Move the full input/output JSON schemas into a references/ file and link to them, keeping only a compact worked example inline.

Replace the all-'string_value' example input with one realistic worked example showing assetRef plus a single patch surface.

Dimension	Reasoning	Score
Conciseness	Mostly efficient prose, but the two large inlined JSON Schema blocks (~140 lines total) are bulky reference material sitting in the main body and could be tightened or externalized.	3 / 5
Actionability	Provides a concrete, mostly copy-paste-ready CLI command with stdin/file variants and troubleshooting, though the example input uses placeholder 'string_value' for every field rather than a realistic worked example.	4 / 5
Workflow Clarity	Patch ordering is specified (jsonPatch -> pathPatches -> content), but this destructive write skill has no validation or verification step, so workflow clarity is capped at 3 per the rubric.	3 / 5
Progressive Disclosure	No bundle files exist and the full input/output JSON schemas are inlined in SKILL.md; content that would benefit from a separate reference file is inline, though headers provide some structure.	3 / 5
	Total	13 / 20 Passed

Description

66%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 specific and well-scoped to asset modification with concrete surfaces and a prerequisite, but lacks an explicit 'when to use' trigger clause, which limits completeness. Trigger term coverage is good but could add the asset-type synonyms users actually say.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers (e.g. 'Use when modifying Materials, ScriptableObjects, Prefabs, or other Assets').

Surface the asset-type keywords (Material, Prefab, ScriptableObject) in the description so they match natural user phrasing.

Consider stating 'when NOT to use' (Packages/ assets) more concisely to sharpen distinctiveness.

Dimension	Reasoning	Score
Specificity	Names the domain ('Modify an asset file') and lists several concrete surfaces (content, pathPatches, jsonPatch) plus a prerequisite (assets-get-data), with minor coverage gaps.	4 / 5
Completeness	Has a clear 'what' but no explicit 'Use when...' trigger clause, so 'when' is only weakly implied; per the rubric this caps completeness at 3.	3 / 5
Trigger Term Quality	Includes natural terms like 'asset file', 'asset structure', 'Assets/', and 'Packages/', but omits common user phrasings (Material, Prefab, ScriptableObject) that only appear in the body.	4 / 5
Distinctiveness Conflict Risk	Scoped to assets-modify, references the sibling assets-get-data skill, and explicitly excludes Packages/, giving it a clear niche with only minor overlap risk.	4 / 5
	Total	15 / 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-modify/SKILL.md
Commit: e873d6c

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