package-remove

Uninstall a UPM package from the Unity project. Modifies `manifest.json` and may trigger a domain reload — the final result is delivered after the reload via the request's `requestId`. Built-in packages and packages that are dependencies of others cannot be removed. Use 'package-list' to list installed packages first.

Quality

76%

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

Quality

Content

85%

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 well-structured with a clear, validated workflow, but loses conciseness through repeated input definitions and a redundant restatement of the description.

Suggestions

Consolidate the packageId definition into a single section; drop either the '## Inputs' list, the Input table, or the JSON Schema to avoid triple repetition.

Remove the opening paragraph that restates the frontmatter description, or replace it with non-duplicative guidance.

Trim the three invocation variants to the recommended stdin form plus a one-line pointer to alternatives.

Dimension	Reasoning	Score
Conciseness	Mostly efficient, but the `packageId` input is restated across three sections (Inputs, the Input table, and the Input JSON Schema) and the opening paragraph rephrases the frontmatter description, adding redundancy that could be tightened.	2 / 3
Actionability	Provides copy-paste-ready, executable commands (`unity-mcp-cli run-tool package-remove --input '...'` and `--input-file` variants) plus a concrete example value (`com.unity.textmeshpro`).	3 / 3
Workflow Clarity	The Behavior section sequences the operation with explicit validation (offline `Client.List` check) and error feedback (`PackageNotFound`, surfacing Unity's error message), appropriate for this single-task skill.	3 / 3
Progressive Disclosure	No bundle files exist and none are needed; the body is organized into clear, well-labeled sections (Inputs, Behavior, How to Call, Troubleshooting, Output), which suffices for a self-contained skill.	3 / 3
	Total	11 / 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 well-scoped with concrete actions and constraints, but lacks an explicit 'when to use' trigger clause and includes technical jargon that weakens natural trigger-term coverage.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to remove or uninstall a Unity package.'

Soften jargon by pairing 'UPM' and 'domain reload' with plain terms users say, like 'Unity package' and 'editor reload'.

Drop the operational detail about requestId delivery from the description; that belongs in the body.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions and constraints: 'Uninstall a UPM package', 'Modifies `manifest.json`', 'may trigger a domain reload', and 'Built-in packages and packages that are dependencies of others cannot be removed'.	3 / 3
Completeness	Clearly states what the skill does, but lacks an explicit 'Use when...' trigger clause; the 'when' is only implied, which caps completeness at 2 per the rubric guideline.	2 / 3
Trigger Term Quality	Has natural terms like 'Uninstall', 'remove', 'package', and 'package-list', but leans on technical jargon ('UPM', 'domain reload', 'requestId') and omits common user phrasings; no explicit trigger phrasing such as 'Use when removing a Unity package'.	2 / 3
Distinctiveness Conflict Risk	Targets a clear niche — removing a Unity project package — with distinct triggers and explicit constraints, making it unlikely to fire for the wrong skill such as package-list or package-add.	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/package-remove/SKILL.md
Commit: e0a24ef

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