CtrlK
BlogDocsLog inGet started
Tessl Logo

profiler-start

Enable Unity's runtime profiler and open the Profiler window. Idempotent: calling when already enabled returns the current enabled state without error.

59

Quality

74%

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

Quality

Content

81%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 a lean, actionable tool reference: a copy-paste-ready command, explicit schemas, useful behavior notes, and troubleshooting. Weaknesses are minor — placeholder example input, no sample output, and boilerplate invocation patterns that could be factored out.

Suggestions

Replace the placeholder example input `{"nothing": "string_value"}` with a real, runnable invocation and add a short example of the returned JSON (e.g. `{"result": true}`).

Fill in the empty Description cell for the `nothing` parameter or drop the parameter row if it is intentionally unused.

Move the generic input-file/stdin invocation boilerplate into a shared reference (e.g. unity-mcp-cli usage) and keep only the direct inline example in this skill, since the boilerplate is identical across sibling tool docs.

DimensionReasoningScore

Conciseness

The body is efficient — one command, an input table, and compact schemas — but the three alternate invocation patterns (inline JSON, --input-file, stdin heredoc) and the empty description cell for the `nothing` parameter are minor padding that could be trimmed. Fits anchor 4 ("Efficient; minor instances of over-explanation"), not anchor 5's "every token earns its place".

4 / 5

Actionability

The CLI command is copy-paste ready and the input/output JSON schemas are concrete, but the example input `{"nothing": "string_value"}` is a placeholder rather than a real working example, and no sample output is shown. Anchor 4 ("Mostly executable guidance... with minor gaps") is the best fit — not 5, whose examples must cover the common cases.

4 / 5

Workflow Clarity

This is a simple single-task skill: the one action (run `unity-mcp-cli run-tool profiler-start`) is unambiguous, and retry semantics are explicitly documented ("Idempotent: calling when already enabled returns the current enabled state without error"). Per the rubric's simple-skill exception, a clear single action scores 5; this is not a batch or destructive operation, so no validation cap applies.

5 / 5

Progressive Disclosure

Single-file body with clear section headers and no nested references; its one external pointer ("Read the /unity-initial-setup skill for detailed installation instructions") is clearly signaled. The generic CLI-invocation boilerplate (~15 lines that recur across sibling tool docs) is content that arguably belongs in a shared reference, keeping this at anchor 4 rather than 5.

4 / 5

Total

17

/

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, concrete, and in third person, with a useful idempotency note. Its main weakness is the complete absence of "when to use this" trigger guidance, which caps completeness and leaves natural trigger terms and synonyms missing.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to profile Unity gameplay or editor performance, enable the Unity Profiler, or start capturing profiling data."

Include natural trigger synonyms such as "profile my game", "performance profiling", or "Unity Profiler" so the skill matches how users actually phrase the request.

Briefly state the tool's niche relative to sibling profiler tools (e.g. it only enables the profiler and does not capture or stream frame data) to reduce overlap risk with related profiler skills.

DimensionReasoningScore

Specificity

"Enable Unity's runtime profiler and open the Profiler window" names the domain plus exactly two concrete actions but is not comprehensive — no mention of what the tool returns beyond the idempotency note. This matches anchor 3 ("Names domain and 1-2 concrete actions, but not comprehensive"), not anchor 4's "several specific actions".

3 / 5

Completeness

The "what" is clear (enable the profiler, open the Profiler window) but there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per judging guidelines. Anchor 3 ("Has a clear 'what' but 'when' is missing") is the best fit — not 4, since the 'when' is entirely absent rather than weakly implied.

3 / 5

Trigger Term Quality

Relevant keywords like "runtime profiler" and "Profiler window" are present, but natural user phrasings ("profile my game", "performance profiling", "enable the profiler") and synonyms are missing. Fits anchor 3 ("Some relevant keywords but missing common variations or synonyms") better than anchor 4's good keyword coverage.

3 / 5

Distinctiveness Conflict Risk

The description targets a specific niche (Unity profiler startup) with concrete, distinct behavior, but "Profiler" could overlap with sibling profiler skills (e.g. profiler-stop, frame capture) without trigger phrasing to distinguish them. Anchor 4 ("Mostly distinct; minor overlap risk with closely related skills") fits; not 5 since no explicit triggers carve out its niche.

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.

Validation — 16 / 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.