reflection-method-call

Call a C# method by reflection — including private methods. Requires a method schema obtained via 'reflection-method-find'. Supports static methods, instance methods (with optional target deserialization), and main-thread / off-thread execution.

Quality

56%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./Unity-MCP-Plugin/.claude/skills/reflection-method-call/SKILL.md

Quality

Content

42%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 delivers real invocation commands and schemas but is padded with duplicated, inlined JSON schemas and a redundant parameter table, and lacks a realistic worked example and clear workflow checkpoints.

Suggestions

Move the full input/output JSON schemas into a reference file (e.g. references/schema.json) and keep only a concise parameter summary in SKILL.md to cut duplication.

Replace the placeholder-filled example with a realistic, copy-paste-ready call using actual type/method names and a real inputParameters entry.

Make the find-then-call workflow explicit as a short numbered sequence, and add a validation step for inspecting/handling the returned result or errors.

Dimension	Reasoning	Score
Conciseness	Noticeable padding: the full input and output JSON schemas (~120 lines) are inlined and largely restated by a separate parameter table, with two overlapping 'Inputs'/'Input' sections — content that could be trimmed or moved to references.	2 / 5
Actionability	Provides concrete CLI invocation patterns (run-tool, --input-file, stdin pipe) and troubleshooting, but the main example is filled with placeholder values ('string_value', match levels 0) rather than a realistic, copy-paste-ready call.	3 / 5
Workflow Clarity	The prerequisite sequence (find method with reflection-method-find, then call) is only weakly implied in one sentence, with no validation or error-handling checkpoint for the result.	3 / 5
Progressive Disclosure	Section headers provide some structure, but the bulky JSON schemas that would belong in a separate reference file are inlined in SKILL.md, and the only external pointer is to the unrelated /unity-initial-setup skill.	3 / 5
	Total	11 / 20 Passed

Description

70%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-targeted description with concrete capabilities and low conflict risk, but it lacks an explicit 'Use when...' trigger clause, which limits its completeness.

Suggestions

Add an explicit 'Use when...' clause stating when Claude should invoke this skill (e.g., 'Use when the user asks to invoke or test a C# method, including private or static methods, in a Unity project').

Include a few natural synonyms/variants users might say (e.g., 'invoke method', 'call function', 'run Unity method') to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Lists several concrete capabilities — 'Call a C# method by reflection', 'including private methods', 'static methods, instance methods (with optional target deserialization)', and 'main-thread / off-thread execution' — with only minor coverage gaps.	4 / 5
Completeness	The 'what' is clear, but there is no 'Use when...' trigger clause — only a prerequisite ('Requires a method schema obtained via reflection-method-find') — which caps completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Natural phrases a C#/Unity user would say ('call a C# method', 'reflection', 'private methods') are present, though synonym/extension coverage is limited.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (reflection method invocation in C#/Unity) and names a specific companion skill, giving it distinct triggers with minimal overlap risk.	5 / 5
	Total	16 / 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/reflection-method-call/SKILL.md
Commit: 07b8f65

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