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

66%

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

67%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 well-structured with concrete, executable CLI examples and built-in validation behavior for a destructive operation. Its main weaknesses are redundancy — the intro repeats the description and `packageId` is documented in two separate sections — which hurts conciseness and organization.

Suggestions

Merge the duplicate `## Inputs` and `## Input` sections into a single parameter description to remove redundancy.

Trim the intro paragraph so it does not restate the frontmatter description verbatim.

Replace the `"string_value"` placeholder in the CLI example with a real package ID (e.g. `com.unity.textmeshpro`) to make the example fully concrete.

Dimension	Reasoning	Score
Conciseness	The intro paragraph restates the frontmatter description ("Note: Built-in packages...", "Note: Package removal may trigger a domain reload...") and the `packageId` parameter is described twice in separate `## Inputs` and `## Input` sections, so it is mostly efficient but carries clear redundancy that could be tightened — not as padded as a 2.	3 / 5
Actionability	Provides copy-paste-ready bash invocations (`unity-mcp-cli run-tool package-remove --input '...'`) plus `--input-file` and stdin variants, a concrete input JSON schema, and a troubleshooting fix (`npm install -g unity-mcp-cli`); the placeholder `"string_value"` keeps it just short of the fully-real-example coverage of a 5.	4 / 5
Workflow Clarity	The single destructive action is unambiguous with a documented pre-check ("verifies the package is installed via an offline `Client.List`") and error surfacing ("returns a clear `PackageNotFound` error", "surfaces Unity's error message"), so validation is present and the destructive cap at 3 does not apply; minor gaps (no explicit post-removal verification step) keep it at 4 rather than 5.	4 / 5
Progressive Disclosure	Well-organized with clear section headers and a single clearly-signaled cross-skill reference ("Read the /unity-initial-setup skill"), with no nested references; the duplicated Inputs/Input sections are a minor organization gap that prevents a 5 despite the otherwise clean structure.	4 / 5
	Total	15 / 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.

A specific, technically precise description that clearly conveys what the skill does and its key constraints, but it lacks an explicit "Use when..." trigger clause, which caps completeness. Distinctiveness is strong within the Unity package-management niche.

Suggestions

Add an explicit trigger clause such as "Use when the user asks to uninstall or remove a Unity package" to lift completeness above 3.

Include a couple of natural synonyms (e.g. "delete package") to broaden trigger-term coverage.

Clarify the distinction from package-install/package-list in the description to reduce overlap ambiguity.

Dimension	Reasoning	Score
Specificity	Names the concrete action ("Uninstall a UPM package"), specifics like "Modifies `manifest.json`", "may trigger a domain reload", and the constraint that built-in/dependency packages "cannot be removed" — several specific behaviors with only minor gaps, falling short of the multi-action comprehensiveness of a 5.	4 / 5
Completeness	The "what" is clearly stated, but there is no "Use when..." trigger clause — "Use 'package-list' to list installed packages first" is a precondition, not usage guidance, so per the missing-trigger guideline completeness is capped at 3.	3 / 5
Trigger Term Quality	Natural user phrases "Uninstall a UPM package" and "remove" (skill name) are present alongside domain terms ("Unity project", "manifest.json"); a few common synonyms like "delete package" are missing, so it sits above 3 but below the full synonym/extension coverage of 5.	4 / 5
Distinctiveness Conflict Risk	The niche is specific (removing Unity UPM packages) with distinct "uninstall/remove" triggers and minimal conflict risk, but it shares the package-management domain with sibling skills (package-install, package-list), giving minor overlap risk rather than the clean isolation of a 5.	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/package-remove/SKILL.md
Commit: e873d6c

Reviewed: 1 day 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.