CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

62

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

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
SKILL.md
Quality
Evals
Security

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with executable CLI examples, schemas, and troubleshooting, and the single-tool workflow is unambiguous. Its main weakness is redundancy — inputs appear three times and the intro echoes the frontmatter — which hurts conciseness and keeps progressive disclosure at a single monolithic file.

Suggestions

Collapse the three input representations (## Inputs bullets, ## Input table, Input JSON Schema) into one — keep the table plus the schema, drop the duplicated prose bullets.

Remove the opening body paragraph that restates the frontmatter description verbatim.

Use accurate placeholder values in the How-to-Call example (boolean for includeDescription, enum for includeInputs) instead of 'string_value' so the example is truly copy-paste correct.

DimensionReasoningScore

Conciseness

The same three inputs are restated three times (## Inputs bullets, the ## Input table, and the Input JSON Schema) and the opening paragraph repeats the frontmatter description. It avoids explaining basic concepts, but the redundancy could be tightened.

2 / 3

Actionability

Provides fully executable commands ('unity-mcp-cli run-tool unity-tool-list --input ...', '--input-file', stdin piping), concrete troubleshooting fixes ('npm install -g unity-mcp-cli', 'npx unity-mcp-cli'), and complete input/output JSON schemas — copy-paste ready.

3 / 3

Workflow Clarity

This is a single, unambiguous action (call the tool with optional filter and verbosity toggles) supported by Behavior, How to Call, and Troubleshooting sections; per the simple-skill scoring note, a clear single action warrants 3.

3 / 3

Progressive Disclosure

The single file is well-organized with clear section headers and one signaled cross-skill reference ('Read the /unity-initial-setup skill'), but it is monolithic with no detail files and redundant inline content (inputs described three times) that could be consolidated.

2 / 3

Total

10

/

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 clearly distinct, but it lacks an explicit 'when to use' trigger and leans on technical jargon over natural user phrasing. Adding a 'Use when...' clause with common natural terms would lift the two capped dimensions.

Suggestions

Add an explicit trigger clause, e.g. 'Use when you need to discover or enumerate the available Unity-MCP tools, or filter tools by name/description/argument.'

Soften jargon toward natural phrasing users would say, e.g. 'list Unity tools', 'find available tools', 'search tools by name'.

Keep the concrete actions but trim the technical 'registered in the connected Unity Editor instance' phrasing so the trigger reads more naturally.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'List all Unity-MCP tools registered in the connected Unity Editor instance', 'Optional regex filter matches against tool name, description, and argument names/descriptions', and verbosity toggles. Voice is third-person/imperative ('List', 'matches', 'Use'), so no voice penalty applies.

3 / 3

Completeness

It clearly answers 'what does this do' but provides no 'Use when...' clause or equivalent trigger guidance, so completeness is capped at 2 per the judging guidelines.

2 / 3

Trigger Term Quality

Some relevant terms ('Unity-MCP tools', 'regex filter') appear, but phrasing like 'registered in the connected Unity Editor instance', 'argument names/descriptions', and 'includeDescription / includeInputs toggles' is technical jargon missing common natural variations a user would actually say.

2 / 3

Distinctiveness Conflict Risk

The Unity-MCP tool-listing niche is specific and distinct ('List all Unity-MCP tools registered in the connected Unity Editor instance'), making it unlikely to trigger for the wrong skill.

3 / 3

Total

10

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
IvanMurzak/Unity-MCP
Reviewed

Table of Contents

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.