CtrlK
BlogDocsLog inGet started
Tessl Logo

build-cli

Build the unity-mcp-cli TypeScript CLI tool and link it globally for terminal use.

62

Quality

78%

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 ./.claude/skills/build-cli/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

93%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 an exemplar of a lean, single-purpose build skill: every command is copy-paste ready, conditions for running each step are stated tersely, and verification is built in. The only shortfall is the absence of an explicit fix-and-retry feedback loop in the Report section.

DimensionReasoningScore

Conciseness

Every sentence carries non-obvious, project-specific information ("Only needed if `node_modules/` is missing or `package.json` changed", "Only needed once — after that, `npm run build` alone is sufficient") with zero padding or explanation of concepts Claude already knows, matching the 'lean and efficient' anchor.

5 / 5

Actionability

All guidance is fully executable copy-paste commands (`cd cli && npm install`, `npm run build`, `npm link`, `unity-mcp-cli --version`) with explicit conditional handling via `$ARGUMENTS`, matching the 'fully executable; copy-paste ready' anchor.

5 / 5

Workflow Clarity

The four steps are clearly sequenced with an explicit verification checkpoint and error-surfacing instruction ("If any step failed, show the error output"), but there is no fix-and-retry recovery loop, placing it between the anchor-4 'minor validation gaps' and anchor-5 'feedback loops for error recovery'.

4 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external references, and is organized into clearly labeled step sections plus a Report section, which per the rubric's own guideline earns a 5 with just well-organized sections.

5 / 5

Total

19

/

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 concise, specific to a named tool, and uses third person, but it answers only the 'what' and provides no 'when to use' trigger guidance or keyword variations. It sits clearly in the middle of the rubric scale across all dimensions.

Suggestions

Add an explicit trigger clause, e.g., "Use when the unity-mcp-cli code has changed and needs rebuilding, or when the global `unity-mcp-cli` command is not available."

Broaden trigger coverage with natural synonyms such as "compile", "install", "npm", or "set up the CLI" so users' phrasing matches more readily.

Mention the verification outcome in the description (e.g., "and verify the installed version") so it more comprehensively reflects the skill's actual steps.

DimensionReasoningScore

Specificity

"Build the unity-mcp-cli TypeScript CLI tool and link it globally" names the domain and two concrete actions (build, link), but omits capabilities the body actually covers such as verification, matching the '1-2 concrete actions, but not comprehensive' anchor rather than the 'several specific actions' anchor.

3 / 5

Completeness

The 'what' is stated clearly (build the tool and link it globally), but there is no 'Use when...' or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Terms like "Build", "CLI tool", "link", and "terminal" are relevant and natural for this domain, but no synonyms or variations (e.g., compile, install, npm, TypeScript build) are present, fitting the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The named project "unity-mcp-cli" carves a clear niche with minimal conflict risk, but the generic verbs "Build" and "link" could overlap with other build/setup skills, fitting 'mostly distinct; minor overlap risk' rather than the anchor-5 'distinct triggers' example.

4 / 5

Total

13

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

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.