CtrlK
BlogDocsLog inGet started
Tessl Logo

console-clear-logs

Clear the MCP log cache (used by 'console-get-logs') and the Unity Editor Console window. Useful for isolating logs to a specific action by clearing the slate first.

69

Quality

87%

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

SKILL.md
Quality
Evals
Security

Quality

Content

86%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.

A tight, actionable, well-structured skill body for a simple tool: the call example is executable, troubleshooting is concrete, and sections are logically organized. The only meaningful gap is the absence of a verification step for an operation that irreversibly clears the log cache, plus some boilerplate input scaffolding that could be trimmed.

Suggestions

Add a verification hint, e.g. "After clearing, run console-get-logs to confirm only new entries appear" — the operation wipes the log cache irreversibly.

Trim or collapse the generic --input-file/stdin blockquote, since this tool's only input is the placeholder "nothing" parameter.

Consider dropping or abbreviating the Input table and schema for the no-op "nothing" parameter to save tokens.

DimensionReasoningScore

Conciseness

The body is lean and well organized (Behavior, How to Call, Input, Output), but the generic stdin/--input-file boilerplate and the Input table/schema for the meaningless "nothing" parameter add tokens that could be trimmed. Not 5 because not every token earns its place.

4 / 5

Actionability

The unity-mcp-cli command is copy-paste ready with working JSON, and the Troubleshooting section adds concrete fallbacks (npx, global install, setup skill pointer). No gaps for the common case.

5 / 5

Workflow Clarity

The single action is unambiguous and Behavior sequences the two internal effects, but no verification step exists (e.g. confirming via console-get-logs that the cache is empty) even though the operation irreversibly wipes the log cache. Fits "clear sequence with minor validation gaps" rather than the explicit-validation anchor of 5.

4 / 5

Progressive Disclosure

A sub-50-line single-purpose skill with clean section organization and no bundle files; the only reference (the /unity-initial-setup skill) is one level deep and clearly signaled. Per the simple-skill note, this warrants a 5.

5 / 5

Total

18

/

20

Passed

Description

83%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.

A specific, well-scoped description that clearly states what the tool does and stays highly distinct. Its main weakness is the trigger guidance: the "when" is implied through a usefulness statement rather than an explicit "Use when..." clause, and common synonyms like "reset" or "wipe" are absent.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to reset/wipe the Console, isolate errors for a specific action, or get a clean slate before reproducing a bug."

Include common natural synonyms users might say — "clear the console", "reset logs", "wipe Unity Console" — to broaden trigger matching.

Mention "errors"/"debug logs" explicitly since users often ask in those terms when isolating a problem.

DimensionReasoningScore

Specificity

"Clear the MCP log cache (used by 'console-get-logs') and the Unity Editor Console window" names multiple concrete actions that comprehensively cover this single-purpose tool. Not 4 because there are no gaps in coverage — clearing both caches is everything the tool does.

5 / 5

Completeness

The "what" is explicit (clears the MCP log cache and Console window) and a "when" is present ("Useful for isolating logs to a specific action"), but there is no explicit "Use when..." trigger clause and the when could be more specific. Matches anchor 4 rather than 3 because the when is stated, not merely implied.

4 / 5

Trigger Term Quality

Natural terms like "clear", "log cache", "Unity Editor Console", and "isolating logs" are present and would match user phrasing. Missing common variations such as "reset", "wipe", or "console errors", so it falls short of the comprehensive synonym coverage of a 5.

4 / 5

Distinctiveness Conflict Risk

Naming the MCP log cache, 'console-get-logs', and the Unity Editor Console gives it a clear niche with distinct triggers and minimal conflict risk with other skills.

5 / 5

Total

18

/

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.