CtrlK
BlogDocsLog inGet started
Tessl Logo

console-get-logs

Retrieve Unity Editor logs from the MCP plugin's `LogCollector`, optionally filtered by log type or time window. Useful for debugging and monitoring Editor activity.

58

Quality

73%

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/console-get-logs/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

60%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 well structured and highly actionable, with an excellent polling recipe and practical troubleshooting, but it is notably redundant: the five parameters are documented three times and the intro restates the description. The main example also contains placeholder/contradictory values (maxEntries: 0 vs minimum 1, "string_value") that undercut copy-paste readiness.

Suggestions

Collapse the duplicate parameter documentation: keep either the "## Inputs" prose list or the "## Input" table (the table, ideally, since it adds Type/Required columns) and drop the other, and remove the intro line that restates the frontmatter description.

Fix the example to be copy-paste ready: use a valid maxEntries (e.g. 100, since 0 contradicts the documented minimum of 1) and a real filter value (e.g. "Error" or null) instead of "string_value".

Consider moving the full Input/Output JSON schemas into a references/ file (e.g. SCHEMAS.md) and keeping only a short entry-shape example inline, which would cut the token footprint while preserving the detail on demand.

DimensionReasoningScore

Conciseness

The five input parameters are documented three times — the "## Inputs" prose list, the "## Input" table, and the Input JSON Schema — and the line under the H1 ("Retrieves Unity Editor logs. Useful for debugging and monitoring Unity Editor activity.") restates the frontmatter description. These are whole padded/duplicated sections, matching anchor 2 ('noticeably verbose; several unnecessary explanations or padded sections') rather than anchor 3, because the redundancy is structural, not just occasional over-explanation; it stays above anchor 1 since there is no conceptual padding or tutorial prose.

2 / 5

Actionability

The body provides a concrete executable command ("unity-mcp-cli run-tool console-get-logs --input '...'"), the --input-file and stdin variants, install troubleshooting ("npm install -g unity-mcp-cli" or "npx"), and a concrete polling recipe ("pass the highest sequence you have received as sinceSequence"). It falls short of anchor 5 because the main example contains placeholder values ("logTypeFilter": "string_value" and "maxEntries": 0, which contradicts the stated minimum of 1), so it is not copy-paste ready for a real call; it is above anchor 3 because the commands themselves are executable and the common cases are covered.

4 / 5

Workflow Clarity

For this simple single-tool skill the action is unambiguous, and the Polling section adds a genuine feedback loop with a checkpoint ("if the result has maxEntries entries, call again with the new highest sequence to continue") plus edge-case recovery ("if returned sequences are lower than your cursor, the log restarted"), and Troubleshooting handles CLI-not-found. It misses anchor 5 because the example's "maxEntries": 0 conflicts with the documented "Minimum: 1", a small coherence gap in an otherwise clear sequence.

4 / 5

Progressive Disclosure

This is a single-file skill with no bundle directories; sections are well organized (Inputs, Polling, How to Call, Troubleshooting, Input, Output) and the one external pointer is clearly signaled ("Read the /unity-initial-setup skill for detailed installation instructions"). It fits anchor 4 ('good structure; most content appropriately placed; minor organization gaps') rather than anchor 5 because the duplicated Inputs/Input sections and the two full inline JSON schemas could be consolidated or split out; it is above anchor 3 because navigation is easy and nothing is buried.

4 / 5

Total

14

/

20

Passed

Description

73%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 a strong, third-person, appropriately concise description with a clear what and an explicit (if soft) when clause and low conflict risk. Its main weaknesses are limited action coverage (no polling, stack traces, or entry limits) and missing the natural Unity synonym "console".

Suggestions

Use a "Use when..." trigger clause with concrete phrases, e.g. "Use when debugging Unity Editor issues, checking the Editor console output, or monitoring Editor activity."

Mention the additional concrete capabilities (stack traces, sequence-based polling for new logs, entry-count caps) to raise specificity, and include the natural keyword "console" since Unity users commonly refer to logs as console output.

DimensionReasoningScore

Specificity

"Retrieve Unity Editor logs ... optionally filtered by log type or time window" names the domain and 1-2 concrete actions (retrieve with two filter modes), but omits capabilities like stack-trace inclusion, sequence-based polling, and entry-count control. This matches anchor 3 ('names domain and 1-2 concrete actions, but not comprehensive') rather than anchor 4, which expects several listed actions; it is above anchor 2 because the actions are concrete, not generic.

3 / 5

Completeness

The what is clear ("Retrieve Unity Editor logs from the MCP plugin's LogCollector, optionally filtered by log type or time window") and the when is explicitly stated ("Useful for debugging and monitoring Editor activity"). This is equivalent trigger guidance, so the missing-'Use when' cap at 3 does not apply, but the when is less directive and less specific than anchor 5's concrete trigger phrases, placing it at anchor 4.

4 / 5

Trigger Term Quality

Natural terms users would say are present: "Unity Editor logs", "debugging", "monitoring Editor activity", "log type". It sits between anchor 3 (missing common variations) and anchor 4 (good coverage, a few natural terms missing) and is noticeably above the midpoint because it names the domain, the artifact, and the use cases — though it misses the common Unity synonym "console" and terms like "errors" or "warnings".

4 / 5

Distinctiveness Conflict Risk

"Unity Editor logs from the MCP plugin's LogCollector" carves out a clear niche (Unity Editor logging via this specific plugin) with distinct triggers, so it is unlikely to fire for unrelated skills. It clearly matches anchor 5 rather than anchor 4, which contemplates overlap with closely related skills.

5 / 5

Total

16

/

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.