Content
92%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 tight, well-structured procedural skill with explicit validation checkpoints, concrete commands, and valuable anti-pattern guidance, all at high token efficiency. Its only weakness is that the distance-grab and look-at-move branches give JSON payloads and parameter names rather than complete executable commands like the click branch does.
Suggestions
Show the full command (not just the input JSON payload) for the distance-grab press and release, mirroring the copy-paste-ready `xr select` example used for the click branch.
Provide a complete `xr look-at` invocation with `target` and `moveToDistance` for the MoveFromTarget branch instead of naming the parameters in prose.
Add a brief recovery hint for when a pre-press checkpoint fails (e.g., if `Hovered` is not confirmed after aiming, re-aim at the surface point) to close the only workflow gap.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body explains nothing Claude already knows and spends every line on operational guidance and anti-patterns ("Do not substitute squeeze index `1`; that is the proximity-grab path"), matching the lean, every-token-earns-its-place anchor. | 5 / 5 |
Actionability | The click branch is fully copy-paste ready (`npx @iwsdk/cli xr select --input-json '...'`) and the MoveFromTarget math is concrete (`d = |S - P|`, rim at transform + (0, radius, 0)), but the distance-grab branch shows only the JSON payload without the full command for press/release, and `xr look-at` parameters are named without a complete invocation — minor gaps that fit the "mostly executable" anchor rather than the fully copy-paste-ready one. | 4 / 5 |
Workflow Clarity | The sequence is explicit (locate/aim once → select exactly one branch → act → query) with validation checkpoints throughout: "confirm `Hovered` before pressing", "Query the named application state or control effect after the click; a screenshot alone is not interaction proof", "Query `Grabbed` or transform state while held and after release", and a defined stop condition ("Stop when the real input and resulting named state are proven, leaving all buttons released"). | 5 / 5 |
Progressive Disclosure | No bundle files exist and none are needed; the self-contained body is organized into clear sections (Locate and aim once / Select exactly one branch / Evidence and stopping) with no content that belongs in a separate file, which per the simple-skill guidance earns the top score on well-organized sections alone. | 5 / 5 |
Total | 19 / 20 Passed |