click-target
Find and click a target object in XR. Use when testing UI interactions, clicking buttons, or verifying interactable elements work correctly.
64
76%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.claude/skills/click-target/SKILL.mdQuality
Discovery
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 structurally sound with a clear 'what' and 'when' clause, making it functionally complete. However, it lacks specificity in the concrete actions it performs beyond 'find and click,' and the trigger terms could be broader to capture natural user language variations (e.g., VR, AR, mixed reality). The XR domain provides some distinctiveness but the UI interaction terms risk overlap with non-XR testing skills.
Suggestions
Add more specific concrete actions beyond 'find and click' — e.g., 'locate UI elements by label or position, simulate click/tap interactions, validate element responsiveness in XR scenes'.
Expand trigger terms to include natural variations like 'VR', 'AR', 'mixed reality', 'tap', 'press', 'select', 'interact with object', and any relevant framework names (e.g., Unity XR, OpenXR).
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a domain (XR) and a primary action ('find and click a target object'), but it doesn't list multiple specific concrete actions beyond that. The elaboration mentions 'testing UI interactions, clicking buttons, verifying interactable elements' which adds some specificity but remains somewhat general. | 2 / 3 |
Completeness | The description clearly answers both 'what' (find and click a target object in XR) and 'when' (Use when testing UI interactions, clicking buttons, or verifying interactable elements work correctly), with an explicit 'Use when...' clause. | 3 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'XR', 'click', 'buttons', 'UI interactions', and 'interactable elements', but misses common variations users might say such as 'VR', 'AR', 'mixed reality', 'tap', 'press', 'select', or specific framework terms. Coverage is partial. | 2 / 3 |
Distinctiveness Conflict Risk | The XR context provides some distinctiveness, but 'clicking buttons' and 'UI interactions' are very broad terms that could overlap with general UI testing skills or web testing skills. The XR qualifier helps but the trigger terms are still somewhat generic. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, actionable skill that clearly guides Claude through an 8-step XR interaction workflow. Its strengths are the specific tool calls, concrete parameter values, and explicit validation/retry loops. Minor verbosity in some explanatory bullets prevents a perfect conciseness score, but overall this is a high-quality skill.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient and avoids explaining basic concepts, but some bullet points are somewhat verbose (e.g., explaining what xr_look_at does with 'This orients the headset to face the target'). The tips section adds useful but slightly redundant information. Overall reasonably lean but could be tightened. | 2 / 3 |
Actionability | Every step specifies the exact MCP tool to call with specific parameters. Concrete values are provided (e.g., offset x by +0.25, y by -0.1, z by -0.3; adjust by 0.05-0.1). The example provides real coordinates and expected console log output. While there's no copy-paste code, this is an instruction-only skill with fully specific, executable guidance. | 3 / 3 |
Workflow Clarity | The 8-step workflow is clearly sequenced with explicit validation checkpoints (step 4: screenshot to verify visibility, step 8: verify click via console logs). Feedback loops are present: if target not visible, move closer; if click missed, adjust and retry. Error recovery paths are clearly specified. | 3 / 3 |
Progressive Disclosure | For a skill of this size (~80 lines) with no bundle files, the content is well-organized into clear sections: Arguments, Workflow (numbered steps), Tips, and Example. The structure is appropriate for the complexity level and doesn't need external references. Content is easy to scan and navigate. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- facebook/immersive-web-sdk
- Commit
3a08b40
- Reviewed
Table of Contents
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.