Find and click a target object in XR. Use when testing UI interactions, clicking buttons, or verifying interactable elements work correctly.
npx skills add https://github.com/facebook/immersive-web-sdk --skill click-target
Find a target object in the scene and click it using a controller, then verify the click registered.
$ARGUMENTS should be a description of the target to find (e.g., "the RESTART button", "the scoreboard", "the settings panel").
Use mcp__iwsdk-dev-mcp__scene_get_runtime_hierarchy to find the target object's UUID.
Use mcp__iwsdk-dev-mcp__scene_get_object_transform with the target UUID.
positionRelativeToXROrigin for all positioning operationsUse mcp__iwsdk-dev-mcp__xr_look_at with device headset and the target position.
Use mcp__iwsdk-dev-mcp__browser_screenshot to verify:
mcp__iwsdk-dev-mcp__xr_look_at with moveToDistance to get closerUse mcp__iwsdk-dev-mcp__xr_get_transform to check controller position.
mcp__iwsdk-dev-mcp__xr_get_transformmcp__iwsdk-dev-mcp__xr_set_transformUse mcp__iwsdk-dev-mcp__xr_look_at with the controller device and target position.
Use mcp__iwsdk-dev-mcp__xr_select with the controller device.
Use mcp__iwsdk-dev-mcp__browser_get_console_logs with a pattern to check for expected log messages.
mcp__iwsdk-dev-mcp__scene_get_object_transform on child elements to find exact button positionsTo click the RESTART button on the pong scoreboard:
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.
Run Playwright tests at scale with cloud-hosted browsers and integrated Azure portal reporting.
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.
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.
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.
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.
Always use browser-harness for any web interaction: automation, scraping, testing, or site/app work.
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.
Take facebook/click-target from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
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.