click-target
Skill350 starsChanged 24 days agoMITView on GitHub
Find and click a target object in XR. Use when testing UI interactions, clicking buttons, or verifying interactable elements work correctly.
In this repository13 other files it gives its agents.
- iwsdk-devSkill
- iwsdk-ui-panelSkill
- test-allSkill
- test-audioSkill
- test-ecs-coreSkill
- test-environmentSkill
- test-grabSkill
- test-interactionsSkill
- test-levelSkill
- test-locomotionSkill
- test-physicsSkill
- test-uiSkill
- xr-mode-testSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
18 rules. About 0 are common, 7 are distinctive, and 11 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
11
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 19
Use mcp__iwsdk-runtime__scene_get_runtime_hierarchy to find the target object's UUID.
- Distinctive: line 21
Look for objects with entityIndex (these are ECS entities)
- Very specific: line 26
Use mcp__iwsdk-runtime__scene_get_object_transform with the target UUID.
- Very specific: line 28
Use positionRelativeToXROrigin for all positioning operations
- Very specific: line 33
Use mcp__iwsdk-runtime__xr_look_at with device headset and the target position.
- Very specific: line 39
Use mcp__iwsdk-runtime__browser_screenshot to verify:
- Very specific: line 43
If not visible, use mcp__iwsdk-runtime__xr_look_at with moveToDistance to get closer
- Very specific: line 47
Use mcp__iwsdk-runtime__xr_get_transform to check controller position.
- Distinctive: line 49
If controller is visible in screenshot and not occluding target, proceed
- Distinctive: line 50
If controller is far away or not visible:
- Very specific: line 57
Use mcp__iwsdk-runtime__xr_look_at with the controller device and target position.
- Distinctive: line 60
If the target is a button on a panel, the button may be offset from the panel center
- Very specific: line 64
Use mcp__iwsdk-runtime__xr_select with the controller device.
- Very specific: line 68
Use mcp__iwsdk-runtime__browser_get_console_logs with a pattern to check for expected log messages.
- Distinctive: line 70
If no logs match, the click may have missed - adjust target position and retry
- Very specific: line 76
Use mcp__iwsdk-runtime__scene_get_object_transform on child elements to find exact button positions
- Distinctive: line 77
Always verify with console logs rather than assuming from visuals
- Distinctive: line 89
Verify "[BUTTON CLICKED]" appears in console logs
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Click Target in XR
Find a target object in the scene and click it using a controller, then verify the click registered.
Arguments
$ARGUMENTS should be a description of the target to find (e.g., "the RESTART button", "the scoreboard", "the settings panel").
Workflow
1. Get Scene Hierarchy
Use mcp__iwsdk-runtime__scene_get_runtime_hierarchy to find the target object's UUID.
- Look for objects with entityIndex (these are ECS entities)
- PanelUI elements typically have nested children for their content
2. Get Target Transform
Use mcp__iwsdk-runtime__scene_get_object_transform with the target UUID.
- Use
positionRelativeToXROriginfor all positioning operations - Note the position for the next steps
3. Position Headset to Look at Target
Use mcp__iwsdk-runtime__xr_look_at with device headset and the target position.
- This orients the headset to face the target
4. Screenshot to Verify Target Visible
Use mcp__iwsdk-runtime__browser_screenshot to verify:
- Target is visible in the view
- Target is not occluded by other objects
- If not visible, use
mcp__iwsdk-runtime__xr_look_atwithmoveToDistanceto get closer
5. Position Controller
Use mcp__iwsdk-runtime__xr_get_transform to check controller position.
- If controller is visible in screenshot and not occluding target, proceed
- If controller is far away or not visible:
- Get headset position with
mcp__iwsdk-runtime__xr_get_transform - Set controller to headset position with
mcp__iwsdk-runtime__xr_set_transform - Micro-adjust: offset x by +0.25 (right) or -0.25 (left), y by -0.1, z by -0.3
- Get headset position with
6. Point Controller at Target
Use mcp__iwsdk-runtime__xr_look_at with the controller device and target position.
- For UI elements on panels, you may need to target a specific child element
- If the target is a button on a panel, the button may be offset from the panel center
7. Click
Use mcp__iwsdk-runtime__xr_select with the controller device.
8. Verify Click
Use mcp__iwsdk-runtime__browser_get_console_logs with a pattern to check for expected log messages.
- If no logs match, the click may have missed - adjust target position and retry
- Common adjustments: change x or z by 0.05-0.1 to hit child elements
Tips
- For PanelUI buttons, the button position is often offset from the panel center
- Use
mcp__iwsdk-runtime__scene_get_object_transformon child elements to find exact button positions - Always verify with console logs rather than assuming from visuals
- The ray visual in screenshots can be misleading - test with actual clicks
- Either controller (left or right) can be used
Example
To click the RESTART button on the pong scoreboard:
- Find scoreboard entity (entityIndex 6 in the pong game)
- Scoreboard is at (0, -0.798, -1.25)
- Button is at approximately (0.05, -0.798, -1.109) - offset toward player
- Point controller at button position and click
- Verify "[BUTTON CLICKED]" appears in console logs
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

