profiler-list-modules

List all known profiler module names with their local 'enabled' bookkeeping flag.

Quality

71%

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/profiler-list-modules/SKILL.md

Quality

Content

73%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 well-structured, self-contained tool reference with executable commands and complete schemas, scoring well on actionability and workflow clarity for a simple read-only skill. The main costs are the generic multi-variant invocation boilerplate and the inlined verbose JSON schema.

Suggestions

Trim the three-variant "How to Call" boilerplate to a single recommended invocation (e.g. just the stdin heredoc), since the tool takes no meaningful input.

Replace the placeholder "nothing": "string_value" example with a real minimal call or explicitly note the tool accepts no arguments.

Move the verbose output JSON schema (long CLR-qualified $defs) into a reference file and keep a short summary of the returned fields (Name, Enabled) in SKILL.md.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with short factual sections, but the generic "How to Call" boilerplate repeats three invocation variants (inline, --input-file, stdin heredoc) for a tool whose only input is a no-op "nothing" parameter, which is padding. It is tighter than the noticeably-verbose anchor at 2 but clearly has trimmable content, so it does not reach 4.	3 / 5
Actionability	Concrete, copy-paste-ready CLI commands with a literal JSON payload, an input table, full input/output JSON schemas, and specific troubleshooting steps ("npm install -g unity-mcp-cli", "npx unity-mcp-cli") are all provided. It falls short of 5 only because the example input ("nothing": "string_value") is a placeholder rather than a realistic common case.	4 / 5
Workflow Clarity	This is a simple single-purpose read-only skill and the single action is unambiguous: one command call, fully specified inputs, plus a troubleshooting path if the CLI is missing. Per the simple-skill exception, no validation checkpoints are needed for a non-destructive list operation, so it warrants 5.	5 / 5
Progressive Disclosure	Sections are well-organized (Behavior, How to Call, Troubleshooting, Input, Output) with no external references needed and no nested-reference problem. It does not reach 5 because the bulky output JSON schema (with long CLR-qualified $ref names) is inlined in SKILL.md where a reference file would keep the overview leaner.	4 / 5
	Total	16 / 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 states its single capability concretely and in third person, but it is missing a 'when to use' clause and natural trigger variations, which keeps it at the mid-level across most dimensions. Adding an explicit trigger sentence would raise completeness and trigger-term quality substantially.

Suggestions

Add a 'Use when...' clause, e.g. "Use when the user asks which Unity profiler modules exist or which are enabled, or before toggling modules with profiler-enable-module."

Include natural trigger synonyms such as 'profiling', 'Unity profiler', 'available modules', and 'module flags' so users phrasing the request differently still match.

Optionally mention the pairing with profiler-enable-module in the description itself to sharpen distinctiveness from that sibling skill.

Dimension	Reasoning	Score
Specificity	"List all known profiler module names with their local 'enabled' bookkeeping flag" names the domain and one concrete action (listing modules with their enabled state), matching the anchor for 1-2 concrete actions but not comprehensive coverage. It is more concrete than the generic anchor at 2 ("Processes PDF files"), but does not list several actions needed for 4.	3 / 5
Completeness	The 'what' is clearly stated (list profiler module names and their enabled flags), but there is no 'when' or 'Use when...' clause anywhere in the description, which caps completeness at 3 per the judging guidelines. It is not vague enough to fall to 2, and lacks any 'when' to reach 4.	3 / 5
Trigger Term Quality	Relevant keywords like "profiler", "module names", and "enabled" are present and would match a user asking about profiler modules, but common variations such as "profiling", "Unity profiler", or "available profiler modules" are missing. This sits at 'some relevant keywords but missing common variations', not the fuller coverage of 4.	3 / 5
Distinctiveness Conflict Risk	The description has a clear niche (read-only listing of profiler modules and their enabled state) that is unlikely to trigger for unrelated skills, though it overlaps slightly with a closely related sibling skill ("profiler-enable-module" referenced in the body). This matches 'mostly distinct; minor overlap risk with closely related skills' rather than the minimal-conflict clarity of 5.	4 / 5
	Total	13 / 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/profiler-list-modules/SKILL.md
Commit: 4c8056f

Reviewed: 8 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.