CtrlK
BlogDocsLog inGet started
Tessl Logo

profiler-stop

Disable Unity's runtime profiler. Idempotent — calling when already disabled returns the current disabled state.

57

Quality

65%

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

Quality

Content

71%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 content is well-structured, actionable, and appropriately scoped for a simple single-purpose tool, with clear CLI examples and schemas. Its main weakness is the spurious "nothing" input parameter with an empty description and placeholder payload, which wastes tokens and slightly muddies the otherwise clean documentation.

Suggestions

Remove or clarify the bogus "nothing" input parameter and its empty description, and replace the placeholder example payload with a realistic one (or omit the payload since the tool takes no real input).

Trim the three CLI invocation variants to the essential one or two, keeping only the recommended stdin-pipe form and the basic form.

Add a one-line note to verify success by checking the returned "result" boolean is false.

DimensionReasoningScore

Conciseness

The body is mostly lean, but it documents a meaningless "nothing" string parameter with an empty description and a placeholder example payload ("string_value"), and shows three redundant CLI invocation variants, so it includes unnecessary content that could be tightened.

3 / 5

Actionability

It gives concrete, copy-paste-ready CLI commands (run-tool, --input-file, stdin pipe) plus executable troubleshooting (npx, npm install -g), with the minor gap that the example payload is a placeholder rather than a real common case.

4 / 5

Workflow Clarity

This is a single, non-destructive, non-batch action that is stated unambiguously (Profiler.enabled = false, returns the value), but there is no guidance to verify the returned result is false, a minor checkpoint gap that keeps it just below 5.

4 / 5

Progressive Disclosure

The skill is short and single-purpose with well-organized section headers and one clearly signaled sibling-skill reference (/unity-initial-setup), matching the under-50-lines-no-external-references exception for a top score.

5 / 5

Total

16

/

20

Passed

Description

58%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 specific and behaviorally precise about what the skill does, but it entirely lacks a "when to use it" trigger clause, which caps its completeness and leaves its trigger-term coverage thin. Adding a natural "Use when..." phrase with synonyms (profiling, stop profiling) would lift both completeness and trigger_term_quality.

Suggestions

Add an explicit "Use when..." trigger clause, e.g. "Use when the user wants to stop/disable Unity profiling or turn off the runtime profiler."

Include natural synonyms and variations ("profiling", "stop profiling", "performance profiling") alongside "profiler" to improve trigger-term coverage.

Add a distinguishing cue versus a sibling profiler-start skill so the description alone signals stop vs. start intent.

DimensionReasoningScore

Specificity

"Disable Unity's runtime profiler" names the domain plus a concrete action, and "Idempotent — calling when already disabled returns the current disabled state" adds concrete behavioral detail, matching the minor-gaps anchor rather than the single-action or comprehensive-coverage anchors.

4 / 5

Completeness

It gives a clear "what" (disable the profiler, idempotent) but has no "Use when..." trigger clause, which per the rubric caps completeness at 3; it is not 4 because no explicit "when" is present.

3 / 5

Trigger Term Quality

It includes the natural term "profiler"/"Unity" but misses common variations and synonyms ("profiling", "stop profiling", "performance profiling"), fitting the some-relevant-keywords-but-missing-variations anchor.

3 / 5

Distinctiveness Conflict Risk

"Disable Unity's runtime profiler" is a clear niche with minimal broad conflict risk, but a likely sibling profiler-start skill means minor overlap risk, fitting the mostly-distinct anchor rather than the fully-distinguished anchor that needs explicit triggers.

4 / 5

Total

14

/

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.