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.

Quality

54%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

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

Quality

Content

50%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 gives executable CLI examples and troubleshooting, but is hampered by redundant duplication of the input list and inlined JSON schemas that hurt conciseness and structure. No bundle references exist, so progressive disclosure relies solely on inline organization.

Suggestions

Remove the duplicate input presentation: keep either the bullet list or the markdown table, not both, to reduce token cost.

Replace placeholder values in the example (e.g., 'string_value') with a realistic call showing actual filter values and expected output.

Consider moving the full input/output JSON schemas to a reference file and linking to it, keeping only key fields inline in SKILL.md.

Dimension	Reasoning	Score
Conciseness	The body duplicates the Inputs list as both a bullet list and a full markdown table with identical content, and inlines full input/output JSON schemas that could be referenced separately, adding noticeable redundancy.	2 / 5
Actionability	Provides copy-paste-ready CLI invocation examples including stdin/file variants and a troubleshooting tip, with only minor gaps such as placeholder values like 'string_value' in the example input.	4 / 5
Workflow Clarity	This is a single read-only retrieval skill, so the sequence is trivial, but the example uses placeholder JSON ('string_value', zeros) and offers no validation/verification guidance for confirming results, leaving checkpoints implicit.	3 / 5
Progressive Disclosure	There are no bundle files, and while sections are present, the full input and output JSON schemas are inlined rather than separated; no external references exist, and content that could live in a reference file is inline.	3 / 5
	Total	12 / 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 well-scoped to Unity Editor logs, but lacks an explicit 'Use when...' trigger clause, capping completeness. Trigger term coverage is decent but missing common variations and synonyms.

Suggestions

Add an explicit 'Use when...' clause with concrete trigger phrases (e.g., 'Use when the user asks to check Unity console output, debug Editor errors, or monitor log activity').

Include natural synonyms and Unity-specific terms (e.g., 'console', 'stack traces', 'Editor errors') to improve trigger term coverage.

Distinguish from sibling log skills by noting this is read-only retrieval versus any log-clearing or log-level configuration skill.

Dimension	Reasoning	Score
Specificity	Names the concrete action ('Retrieve Unity Editor logs') and specific capabilities (filtering by log type or time window), with only minor coverage gaps versus the 'several specific actions' anchor.	4 / 5
Completeness	The 'what' is clearly stated but the 'when' is only weakly implied ('Useful for debugging and monitoring'); there is no explicit 'Use when...' trigger clause, which caps completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	Includes natural terms like 'Unity Editor logs', 'debugging', and 'monitoring Editor activity', but misses common synonyms and explicit trigger phrasing users would naturally say.	3 / 5
Distinctiveness Conflict Risk	Scoped to Unity Editor logs via the MCP plugin's LogCollector, a clear niche with minimal overlap risk against other Unity skills, though it could still be confused with a sibling log skill.	4 / 5
	Total	14 / 20 Passed

Validation

100%

Warnings & errors only

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
Path: Unity-MCP-Plugin/.claude/skills/console-get-logs/SKILL.md
Commit: e873d6c

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.