CtrlK
BlogDocsLog inGet started
Tessl Logo

unity-initial-setup

Provides an initial setup for AI Skills, `unity-mcp-cli` command line tool installation and everything else that is helpful to set up at the start of the project. Essential packages, and basic configurations.

52

Quality

57%

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

Quality

Content

65%

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

The content is highly actionable with concrete executable commands and a clear sequence, but it lacks validation checkpoints in the workflow and keeps everything in one moderately long document without progressive disclosure to separate files.

Suggestions

Add explicit validation checkpoints between Quick Start steps (e.g., verify install-plugin succeeded, confirm Unity Editor is running and connected before setup-skills) with a fix-and-retry loop to lift workflow clarity.

Trim explanatory padding such as 'so the command is available system-wide' and the manual Node.js download aside to improve conciseness.

Consider moving the Common Commands Reference table into a separate reference file so SKILL.md stays a lean overview, improving progressive disclosure.

DimensionReasoningScore

Conciseness

The body is mostly efficient and command-focused, but includes light explanatory padding ('so the unity-mcp-cli command is available system-wide', the manual Node.js download aside) that could be tightened.

2 / 3

Actionability

It provides fully executable, copy-paste-ready commands with concrete flags (e.g., 'npm install -g unity-mcp-cli', 'unity-mcp-cli configure <path> --enable-all-tools') and a concrete command reference table.

3 / 3

Workflow Clarity

The Quick Start gives a clear numbered 1–5 sequence, but there are no validation checkpoints or fix-and-retry feedback loops between steps, which caps workflow clarity at 2 for this multi-step setup process.

2 / 3

Progressive Disclosure

Sections are well-organized and self-contained with no nested references, but the 116-line single document keeps all content inline with no external split, leaving structure good but not optimally progressive.

2 / 3

Total

9

/

12

Passed

Description

50%

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 communicates the skill's purpose at a high level but relies on vague filler and lacks an explicit 'Use when...' trigger clause, leaving all dimensions at the mid level.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggers (e.g., 'Use when setting up a Unity project for AI Skills/MCP integration, installing unity-mcp-cli, or configuring MCP for an AI agent') to lift completeness and trigger_term_quality.

Replace vague filler ('everything else that is helpful to set up', 'basic configurations') with concrete actions such as 'install the Unity-MCP plugin, enable tools/prompts/resources, and generate AI skill files' to raise specificity.

Include natural user-facing trigger terms ('Unity', 'MCP setup', 'AI agent integration') so users naturally invoke this skill over generic setup skills.

DimensionReasoningScore

Specificity

It names the domain and concrete actions ('unity-mcp-cli command line tool installation', 'Essential packages, and basic configurations'), but pads these with vague filler like 'everything else that is helpful to set up', so it is not a comprehensive list of specific actions.

2 / 3

Completeness

It states what the skill does but provides no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 2 per the rubric guidelines.

2 / 3

Trigger Term Quality

It includes some relevant keywords ('unity-mcp-cli', 'AI Skills', 'initial setup') but they skew technical and it omits common natural variations a user would say (e.g., 'set up Unity', 'MCP setup').

2 / 3

Distinctiveness Conflict Risk

The 'unity-mcp-cli' tool name gives it a distinct niche, but generic surrounding language ('initial setup', 'basic configurations') could overlap with other project-setup skills and there are no distinct explicit triggers.

2 / 3

Total

8

/

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.