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

67%

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

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with concrete, executable CLI examples and clear organization, and the single-step read-only workflow is unambiguous. Its main weakness is redundancy in how inputs are presented and the inlining of large JSON schemas that could be split into reference files.

Suggestions

Remove redundancy by presenting input parameters in only one form (e.g., keep the table and JSON schema, drop the duplicate prose list, or vice versa).

Consider moving the full input/output JSON schemas into a separate reference file referenced from the body to improve progressive disclosure.

Add a brief note on interpreting the returned LogEntry fields (e.g., LogType severity, Timestamp format) to make the output more immediately usable.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient reference material with no concept-explaining fluff, but the inputs are described three times (prose list, table, and JSON schema), which is redundant and could be tightened.	2 / 3
Actionability	It provides fully executable, copy-paste-ready CLI commands including --input, --input-file, stdin piping, and a troubleshooting install fallback, matching the anchor-3 example of concrete executable guidance.	3 / 3
Workflow Clarity	This is a single-purpose, read-only retrieval skill whose single action is unambiguous, which per the simple-skills note can score 3; it also includes a troubleshooting checkpoint for when the CLI is missing.	3 / 3
Progressive Disclosure	Sections are well-organized, but no bundle files exist and large inline JSON schemas (input/output) that could live in separate reference files are kept inline, fitting the anchor-2 pattern of content that should be separate being in the main file.	2 / 3
	Total	10 / 12 Passed

Description

57%

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 clearly niched to Unity Editor log retrieval via the MCP plugin, with good distinctiveness. It falls short on completeness and trigger coverage because the 'when to use' guidance is only implied rather than an explicit 'Use when...' clause, and it lacks common keyword variations.

Suggestions

Add an explicit trigger clause such as 'Use when debugging Unity Editor issues, inspecting console output, or filtering logs by severity or time window.'

Include more natural trigger terms a user might say, such as 'console', 'error logs', 'exceptions', or 'stack traces'.

Optionally enumerate concrete actions (retrieve, filter, inspect stack traces) to raise the specificity score.

Dimension	Reasoning	Score
Specificity	It names the core action ('Retrieve Unity Editor logs') and two filter dimensions ('log type or time window'), but presents one primary action with options rather than multiple distinct concrete actions as the anchor-3 example requires.	2 / 3
Completeness	The 'what' is clearly stated, but the 'when' is only an implied general statement ('Useful for debugging and monitoring Editor activity') rather than an explicit 'Use when...' trigger clause, which per the guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	Natural terms like 'logs', 'debugging', 'Unity Editor', and 'filtered by log type' are present, but common variations a user might say (e.g., 'console', 'error logs', 'stack trace') are missing.	2 / 3
Distinctiveness Conflict Risk	The phrase 'Unity Editor logs from the MCP plugin's LogCollector' defines a clear, narrow niche with distinct triggers that is unlikely to conflict with other skills.	3 / 3
	Total	9 / 12 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: e0a24ef

Reviewed: about 12 hours 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.