$ ~/registry/skill/facebook-claude-skills-click-target

SKILL

click-target

Name: click-target
Author: facebook

Find and click XR target objects to verify UI interactions work correctly.

Stars

★ 357

Source

GitHub

Updated

2026-07-08

// securityCaution

Prompt only, no code
Open source

Summary

The material indicates a prompt-only, open-source XR testing workflow with no required secrets and no declared remote endpoints, so overall risk is low. Caution mainly comes from the fact that it instructs use of underlying MCP tools for scene inspection, screenshots, and XR device control, but those capabilities belong to the underlying tools rather than the skill itself.

CredentialsLow risk

The material explicitly states that no keys or environment variables are required, and it does not request account credentials, tokens, or other sensitive secrets, so credential exposure risk is low.

Network egressLow risk

No remote endpoints or external service connections are declared; the README describes local/in-scene XR testing steps only, with no factual indication that user data is sent to outside hosts.

Code executionLow risk

The system flags it as prompt-only; the document merely instructs use of existing MCP interfaces for inspection, positioning, clicking, and log verification, with no indication that the skill itself executes local code, starts processes, or requests extra system privileges.

Data accessCaution

The README explicitly uses scene hierarchy inspection, object transform queries, screenshots, and console log checks, meaning it can access scene structure, visuals, and runtime logs; this is a normal data-access surface for XR/MCP testing tools, with no evidence of overreach beyond the stated purpose.

Supply chainCaution

Positive factors are that it is open-source on GitHub and auditable; however, the repository has 0 stars, no declared license, and unknown maintenance status, so provenance and maintenance confidence are limited. This warrants caution on the supply-chain side, but not a high-risk rating by itself.

Recommendations

Use it only in a trusted XR/MCP testing environment and verify the permission boundaries of the underlying mcp__iwsdk-dev-mcp tools.
If screenshots or console logs are involved, first confirm they do not contain sensitive visuals, personal data, or secret configuration values.
Review the actual GitHub repository code, commit history, and dependency list before adopting it into formal workflows.
In production or shared environments, limit this type of interaction-testing tool's access to scene data and logs.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "click-target" skill from askskill:
1. Download https://raw.githubusercontent.com/facebook/immersive-web-sdk/main/.claude/skills/click-target/SKILL.md
2. Save it as ~/.claude/skills/click-target/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// examples

Test an XR button click

Prompt

Find the “Start” button in the current XR scene and click it. Confirm it is selectable and that clicking it moves to the next step.

Expected

Clicks the target button and reports whether selection and interaction were triggered successfully.

Verify an interactable element

Prompt

Locate the toggle control in the settings panel within the XR interface and click it. Check whether it responds and changes state.

Expected

Identifies and clicks the specified control, then reports whether it responded and changed state.

Run an interaction regression test

Prompt

Find and click the “Confirm Submit” button in the XR prototype to regression-test whether the interaction still works after recent updates.

Expected

Performs the click action and reports whether the interaction works normally or shows failures.

// docs

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-dev-mcp__scene_get_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-dev-mcp__scene_get_object_transform with the target UUID.

Use positionRelativeToXROrigin for all positioning operations
Note the position for the next steps

3. Position Headset to Look at Target

Use mcp__iwsdk-dev-mcp__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-dev-mcp__browser_screenshot to verify:

Target is visible in the view
Target is not occluded by other objects
If not visible, use mcp__iwsdk-dev-mcp__xr_look_at with moveToDistance to get closer

5. Position Controller

Use mcp__iwsdk-dev-mcp__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:
1. Get headset position with mcp__iwsdk-dev-mcp__xr_get_transform
2. Set controller to headset position with mcp__iwsdk-dev-mcp__xr_set_transform
3. Micro-adjust: offset x by +0.25 (right) or -0.25 (left), y by -0.1, z by -0.3

6. Point Controller at Target

Use mcp__iwsdk-dev-mcp__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-dev-mcp__xr_select with the controller device.

8. Verify Click

Use mcp__iwsdk-dev-mcp__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-dev-mcp__scene_get_object_transform on 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