mcpbeat Sign in

Click Target Agent Skill

Find and click a target object in XR. Use when testing UI interactions, clicking buttons, or verifying interactable elements work correctly.

805 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
361
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/facebook/immersive-web-sdk --skill click-target

The instruction itself

13 sections, as written by the author

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_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-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:
  • Get headset position with mcp__iwsdk-dev-mcp__xr_get_transform
  • Set controller to headset position with mcp__iwsdk-dev-mcp__xr_set_transform
  • 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

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

Other skills for the same job

different authors, same section of the catalogue
Webapp Testing
by anthropics
vendor ×12

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

6k tokens scripts
Azure Microsoft Playwright Testing Ts
by lingxling
×1

Run Playwright tests at scale with cloud-hosted browsers and integrated Azure portal reporting.

2k tokens
Chrome Devtools
by christophacham
×1

Browser debugging, performance profiling, and automation via Chrome DevTools MCP. Use when user says "debug this page", "take a screenshot", "check network requests", "profile performance", "inspect console errors", or "analyze page load". Do NOT use for full E2E test suites (use playwright-skill) or non-browser debugging.

1k tokens
QA
by browser-use

QA-test a website or web app and return a 1-5 quality score (5 = flawless, 1 = broken) with evidence. Use when the user wants to test, QA, evaluate, score, or "check how good" a site, page, flow, or app — including a local dev server (e.g. "qa test localhost:5173", "does the checkout work?", "rate this landing page"). Drives a real Browser Use cloud browser, tunneling localhost automatically.

9k tokens
Playwright Component Testing
by microsoft
vendor

Set up component testing with Playwright using a story gallery — scaffold stories and a gallery dev page driven by the built-in mount fixture, no dedicated component-testing runtime. Use when asked to test React or Vue components in isolation with Playwright, or to migrate off @playwright/experimental-ct-react / -vue.

8k tokens scripts
Browser Testing With Devtools
by addyosmani

Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be configured.

4k tokens
Browser Harness
by browser-use

Always use browser-harness for any web interaction: automation, scraping, testing, or site/app work.

493k tokens scripts
Help Center UI Test
by Automattic

Run a browser-based UI review of the WordPress.com Help Center across multiple surfaces, looking for visual and behavioral issues. Use when asked to test the Help Center UI.

2k tokens

How to use it

Copy the folder

Take facebook/click-target from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.