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.

51

Quality

56%

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

58%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 well-structured and gives executable CLI guidance with a useful troubleshooting pointer, but it is padded by repeated command variants and a duplicated input table, and it lacks explicit validation/checkpoint guidance for verifying call results. Consolidating the call examples and adding a brief verify-the-output step would improve both conciseness and workflow clarity.

Suggestions

Collapse the three near-identical 'How to Call' variants into one canonical command plus a single short note on --input-file / stdin, removing the duplicated boilerplate.

Merge the ## Inputs bullet list and the Input table into a single source of truth to eliminate redundancy.

Add a brief validation note for the call result (e.g. check the returned tool list is non-empty or how to interpret an empty/error result) to add an explicit checkpoint.

DimensionReasoningScore

Conciseness

The body is mostly efficient (Inputs/Behavior/How to Call/tables), but the 'How to Call' section repeats the same command three times with near-identical boilerplate and the Input table duplicates info already given in ## Inputs, adding padding.

3 / 5

Actionability

It provides copy-paste ready CLI commands with concrete --input JSON, plus troubleshooting for the missing-CLI case; the placeholder 'string_value' values in the example are a minor gap but the structure is executable.

4 / 5

Workflow Clarity

Behavior describes the single flow at a high level but there are no explicit validation checkpoints or error-recovery feedback loops; the troubleshooting note covers only CLI-not-found rather than validating tool execution results.

3 / 5

Progressive Disclosure

Sections are clearly organized (Inputs, Behavior, How to Call, Input table, schemas, Output) with schemas kept inline but well-delimited; no bundle files exist so structure relies on in-file sections, which are well ordered with only minor redundancy between ## Inputs and the Input table.

4 / 5

Total

14

/

20

Passed

Description

53%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 concrete and well-scoped to a specific runtime, but it lacks an explicit 'Use when...' trigger clause and uses somewhat technical phrasing rather than natural user keywords. Tightening the trigger language and adding a when-to-use clause would lift completeness and trigger quality.

Suggestions

Add a 'Use when...' clause (e.g. 'Use when you need to discover or find a specific Unity-MCP tool') so Claude knows when to invoke this skill.

Include natural user-facing synonyms such as 'see available tools', 'find a tool', or 'search Unity tools' alongside the technical 'regex filter' phrasing.

Name one or two more concrete outcomes (e.g. 'discover available tools and inspect their inputs') to broaden coverage beyond just 'list'.

DimensionReasoningScore

Specificity

Quotes 'List all Unity-MCP tools' and 'filter by regex across tool names, descriptions, and arguments' name the domain plus one concrete action (list) and one filtering action, but coverage is narrow — no enumeration of what 'tools' surface beyond listing.

3 / 5

Completeness

It clearly answers 'what' (list and filter tools, control response size via toggles) but has no 'when/Use when...' clause, so per the guideline a missing trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Natural terms like 'Unity-MCP tools', 'regex filter', 'tool name', and 'inputs' are present, but the phrasing is technical and omits common user-facing synonyms a user would naturally say (e.g. 'see available tools', 'find a tool').

3 / 5

Distinctiveness Conflict Risk

'Unity-MCP tools registered in the connected Unity Editor instance' is a clear niche tied to a specific plugin runtime, with only minor overlap risk against other Unity-MCP tool skills.

4 / 5

Total

13

/

20

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.