Content
67%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A lean, actionable single-tool skill with copy-paste CLI examples, sensible troubleshooting, and explicit error and lifecycle behavior. Weaknesses are duplication (two input sections describing the same parameter), a placeholder example that doesn't conform to the input schema, and the inlined 50-line JSON schema.
Suggestions
Merge the duplicate "## Inputs" and "## Input" sections into one, keeping the table plus a one-line behavioral note.
Replace the placeholder '{"gameObjectRef": "string_value"}' with a realistic example matching the schema, e.g. '{"gameObjectRef": {"instanceID": 12345}}' or a hierarchy-path form.
Move the verbose Input JSON Schema into a separate reference file (or trim it to the fields that matter), keeping SKILL.md as a lean overview.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body documents gameObjectRef twice ("## Inputs" and the "## Input" table with near-duplicate text) and inlines a ~50-line machine-generated JSON schema. It avoids over-explaining known concepts, so it is not anchor 2, but the clear duplication and tightening opportunities match anchor 3 rather than anchor 4. | 3 / 5 |
Actionability | Copy-paste-ready CLI commands are given ("unity-mcp-cli run-tool assets-prefab-open --input ...", the --input-file and heredoc stdin patterns, plus concrete troubleshooting commands). Anchor 4 rather than 5 because the example placeholder '{"gameObjectRef": "string_value"}' does not match the schema (an object with an integer instanceID), leaving no realistic filled-in invocation. | 4 / 5 |
Workflow Clarity | The open → modify → close lifecycle is sequenced ("In the Edit mode you can modify the prefab", "Please use 'assets-prefab-close' tool later to exit prefab editing mode") with explicit error signaling ("Throws when the GameObject cannot be resolved"). This matches anchor 4 — clear sequence with minor validation gaps, namely no way to confirm the stage actually opened given "This tool does not return structured output". | 4 / 5 |
Progressive Disclosure | No bundle files exist and the skill is organized into clear sections (Inputs, Behavior, How to Call, Troubleshooting, Input, Output). Minor gaps — the inlined JSON schema reference material and the duplicated input sections — place it at anchor 4 rather than the well-split, easy-navigation ideal of anchor 5. | 4 / 5 |
Total | 15 / 20 Passed |