unity-tool-list

List all Unity-MCP tools registered in the connected Unity Editor instance. Optional regex filter matches against tool name, description, and argument names/descriptions. Use the `includeDescription` / `includeInputs` toggles to control the response size.

Quality

75%

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/unity-tool-list/SKILL.md

Quality

Content

63%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 the single-step workflow is clear with a useful troubleshooting section, but it is padded by triplicated input documentation and a large inline output schema with no progressive-disclosure layer. Consolidating the input sections and moving the schemas to reference files would tighten it substantially.

Suggestions

Collapse the three overlapping input sections ("## Inputs" prose, "## Input" table, and the Input JSON Schema) into one canonical section — the table plus type information — to remove the redundancy dragging conciseness.

Replace the `"string_value"` placeholders in the example command with type-correct sample values (e.g., `{"includeDescription": true, "includeInputs": "InputsWithDescription"}`) so the example is copy-paste executable.

Move the Input/Output JSON schemas into a `references/schemas.md` (or similar) file and link to it from the body, keeping SKILL.md a lean overview with well-signaled one-level-deep references.

Dimension	Reasoning	Score
Conciseness	The same input documentation appears three times (prose "## Inputs", the "## Input" table, and the "Input JSON Schema"), and the opening sentence repeats the description verbatim. It avoids explaining concepts Claude already knows, but the redundancy is more than trivial and could be tightened into one canonical section.	3 / 5
Actionability	Concrete runnable guidance: the `unity-mcp-cli run-tool unity-tool-list --input '{...}'` command, `--input-file`/stdin heredoc variants, and a CLI-not-found troubleshooting path. Minor gap: the example uses `"string_value"` placeholders for `includeDescription` (a boolean) and `includeInputs` (an enum), which is not copy-paste ready and misleads on types.	4 / 5
Workflow Clarity	As a simple single-purpose skill the call is unambiguous, with troubleshooting feedback for the common failure (CLI not installed). Scored 4 rather than 5 because the near-duplicate "## Inputs"/"## Input" sections and the oddly nested "### Troubleshooting" under "How to Call" blur the document's structure.	4 / 5
Progressive Disclosure	No bundle files exist (no references/, scripts/, or assets/), yet ~60 lines of generated output-schema JSON are inlined in the body — reference-shaped content that would sit better in a references/ file. Sections exist and navigation is possible, so this lands on anchor 3 rather than 2.	3 / 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, distinctive description that accurately captures the tool's full behavior surface, but it lacks any explicit "when to use" trigger guidance and offers few synonym-style natural trigger phrases. Adding a Use-when clause would lift both completeness and trigger-term quality.

Suggestions

Append an explicit trigger clause such as "Use when the user asks what Unity-MCP tools are available, wants to search/filter registered tools, or needs to inspect a tool's inputs" to satisfy the missing 'when' and raise completeness above the cap of 3.

Include natural user phrasings and synonyms (e.g., "available tools", "list Unity tools", "tool registry") alongside the technical terminology to broaden trigger-term coverage.

State the "when" in terms of the user's goal (discovering or inspecting Unity Editor MCP capabilities) rather than only the mechanism, so it competes better against neighboring Unity-MCP skills.

Dimension	Reasoning	Score
Specificity	"List all Unity-MCP tools registered in the connected Unity Editor instance. Optional regex filter matches against tool name, description, and argument names/descriptions. Use the `includeDescription` / `includeInputs` toggles to control the response size." names the core action plus every parameter behavior (filter match targets, verbosity toggles), giving comprehensive coverage with no gaps.	5 / 5
Completeness	The "what" is clear and detailed, but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines; a "when" is only weakly implied by "connected Unity Editor instance".	3 / 5
Trigger Term Quality	Good keyword coverage with domain-natural terms like "Unity-MCP tools", "Unity Editor", "regex filter", and "tool name", but common variations users might say (e.g., "available tools", "search Unity tools", "tool registry") are missing.	4 / 5
Distinctiveness Conflict Risk	"List all Unity-MCP tools registered in the connected Unity Editor instance" carves out a clear niche (Unity-MCP tool enumeration) with distinct triggers and minimal risk of firing for unrelated 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/unity-tool-list/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.