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

66%

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

65%

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 executable CLI examples and useful troubleshooting, but it is weakened by redundant inline JSON schemas that belong in separate reference files and by an implied rather than explicit find-then-call workflow without validation checkpoints.

Suggestions

Move the large Input/Output JSON schemas into a referenced file (e.g. references/schema.md) and link to it from SKILL.md to improve progressive disclosure and reduce token cost.

Formalize the workflow as numbered steps — find the method schema with reflection-method-find, assemble parameters, call, then verify the returned result — including a validation checkpoint.

Trim the restated intro paragraph since it duplicates the frontmatter description, and avoid repeating parameter descriptions that the schema already provides.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient prose but the intro restates the description ('Call C# method. Any method could be called...') and the full Input/Output JSON schemas inline duplicate the parameter table, adding tokens Claude does not need. Not score 3 due to this redundancy; not score 1 because no basic concepts are over-explained and the reference material is relevant.	2 / 3
Actionability	The 'How to Call' section provides copy-paste-ready executable bash commands including the stdin pipe and --input-file variants, plus concrete troubleshooting install commands ('npm install -g unity-mcp-cli' / 'npx'). This matches the anchor for fully executable, specific, copy-paste-ready guidance.	3 / 3
Workflow Clarity	A prerequisite sequence is implied ('Use reflection-method-find to find available method before using it') but it is stated only in prose with no numbered steps or validation checkpoint before calling, and the only error recovery is the CLI-not-found troubleshooting note. Not score 3 because the find-then-call sequence and verification are implicit; not score 1 because a sequence and a fallback are present.	2 / 3
Progressive Disclosure	Sections are organized (Match levels, Inputs, How to Call, Input, Output) but no bundle files exist and the large input/output JSON schemas are inlined in SKILL.md rather than split into a referenced file, matching the anchor for content that should be separate sitting inline. Not score 3 because content is not appropriately split with one-level-deep references; not score 1 because organization is reasonable and references are not deeply nested.	2 / 3
	Total	9 / 12 Passed

Description

67%

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 distinguishes a clear, narrow niche, but it omits any explicit 'Use when...' trigger guidance and leans on internal jargon ('method schema', 'target deserialization'), which limits trigger-term quality and completeness.

Suggestions

Add an explicit trigger clause, e.g. 'Use when you need to invoke a C# method by reflection, call private/internal methods, or execute Unity methods from main or off-thread contexts.'

Soften internal jargon by mentioning natural user phrasings such as 'invoke a method', 'call a private method', or 'run a Unity method' to improve trigger-term coverage.

Clarify the relationship to 'reflection-method-find' as a prerequisite step so the activation condition is unambiguous.

Dimension	Reasoning	Score
Specificity	Quotes 'Call a C# method by reflection — including private methods' and 'Supports static methods, instance methods (with optional target deserialization), and main-thread / off-thread execution' — multiple specific concrete capabilities are listed, matching the anchor for listing several specific actions rather than just naming a domain.	3 / 3
Completeness	The 'what' is clearly and thoroughly stated, but there is no 'Use when...' clause or equivalent explicit trigger guidance for when to invoke the skill, which per the judging guidelines caps completeness at 2. It is above 1 because the capability description is strong, not 3 because 'when' is entirely missing.	2 / 3
Trigger Term Quality	Relevant domain terms appear ('C# method', 'reflection', 'private methods', 'static/instance methods') but phrases like 'method schema obtained via reflection-method-find' and 'target deserialization' are internal jargon; common natural variations a user would say are not comprehensively covered. Not score 3 because natural-term coverage is incomplete, not score 1 because several genuinely usable keywords are present.	2 / 3
Distinctiveness Conflict Risk	The niche is precise and unusual — invoking C# methods by reflection including private members, tied to the 'reflection-method-find' companion — making it unlikely to trigger for the wrong skill. It is above 2 because the specialization is narrow and distinct rather than broadly overlapping.	3 / 3
	Total	10 / 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/reflection-method-call/SKILL.md
Commit: e0a24ef

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