Content
83%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.
An efficient, fully executable CLI reference with excellent conciseness and actionability. Its main weakness is workflow guidance: no validation checkpoints around scene-mutating and batch export operations, and no stated composition of steps (e.g. validate then run, check engine status first).
Suggestions
Wire validation into the workflows: after scene add-node suggest 'scene read' to verify the node landed, and before/after export build suggest checking 'export presets' output or the produced artifacts.
Add a brief recommended sequence for the highest-risk flows, e.g. 'script validate scripts/player.gd' before 'script run', and 'engine status' before any project command to confirm the binary is available.
Consider moving the full command catalog into a references/ file (one level deep, clearly signaled) and keeping SKILL.md to install, requirements, and the most common commands.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is a lean command reference — e.g. "cli-anything-godot -p <project> scene create scenes/Level1.tscn --root-type Node3D" — with no concept explanations, no padding, and no over-explanation of things Claude already knows. Every section earns its tokens; the one-line intro is the only mild redundancy with the frontmatter. | 5 / 5 |
Actionability | Every command is copy-paste ready with concrete flags, placeholders, and realistic values ("--preset 'Windows Desktop' --output build/game.exe"), covering the common case for each command group. The note that script run files "must extend SceneTree" supplies exactly the key detail needed to avoid a failure. | 5 / 5 |
Workflow Clarity | Each command is individually unambiguous, but mutating and batch operations ("export build", "scene add-node", "project reimport") have no validation or verification steps, and "script validate" is never wired into a run workflow. The missing-validation cap for destructive/batch operations holds this at 3 rather than 4. | 3 / 5 |
Progressive Disclosure | Sections are well-organized by command group with clear headers and no buried or nested references, and no bundle files exist to misroute. It is not 5 because the skill exceeds 50 lines with the entire command catalog inlined in SKILL.md — the under-50-line exception doesn't apply — though the catalog is compact enough that inlining is defensible. | 4 / 5 |
Total | 17 / 20 Passed |