$ loading_
Test Havok physics behaviors with the iwsdk CLI against example scenes.
The material appears to be a prompt/instruction set for testing a physics example, and the system flags it as prompt-only with no secrets and no remote endpoints, indicating low overall risk. The README does include local command execution and dependency installation instructions, but these read like test workflow guidance; without actual execution privileges, no concrete high-risk red flags are evident.
The material explicitly states that no keys or environment variables are required, and it does not request accounts, tokens, or other sensitive credentials, so credential exposure and abuse risk is low.
The system checks indicate no remote endpoints; the documentation focuses on a local example workspace and local dev-server interaction, with no declared transmission of user data to third-party hosts.
The README explicitly instructs running local commands such as npm, npx, and sleep, and starting a dev server and test commands; local process launch and command execution are normal capabilities for this kind of skill and warrant attention to the execution environment and command source, but this alone is not a high-risk red flag.
The documentation requires operating inside a local example workspace and may read the project directory, logs, and test outputs; this implies ordinary access to local workspace data, but the material does not show excessive permissions beyond the stated purpose.
A positive factor is that it is declared open source and hosted on GitHub, which provides some auditability; however, the repo has 0 stars, no declared license, unknown maintenance status, and the README mentions installing/invoking dependencies via npm/npx, so supply-chain transparency and maintenance signals are weak and should be verified carefully.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "test-physics" skill from askskill: 1. Download https://raw.githubusercontent.com/facebook/immersive-web-sdk/main/.claude/skills/test-physics/SKILL.md 2. Save it as ~/.claude/skills/test-physics/SKILL.md 3. Reload skills and tell me it's ready
Use the iwsdk CLI to run the physics example, test gravity in the Havok physics system, and explain whether object falling matches expectations.
A gravity test result describing whether objects fall correctly and whether any anomalies are found.
Use the iwsdk CLI to test the physics example, compare static and dynamic rigid body behavior in Havok, and summarize collision results.
A comparison of static and dynamic rigid body behavior, including whether collision responses match expectations.
Run Havok tests on the physics example, check for issues in gravity, rigid bodies, and collision settings, and list possible problem areas.
A diagnostic result identifying abnormal behavior, possible causes, and next troubleshooting steps.
Run 5 test suites covering gravity, static body verification, PhysicsBody state, system/component registration, and stability.
Configuration:
$IWSDK_REPO_ROOT/examples/physicsTool calls: every tool call is npx iwsdk <subcommand> [--input-json '<JSON>'] [--timeout <ms>], run from inside the example workspace (cwd $EXAMPLE_DIR). The CLI auto-discovers the IWSDK app root from cwd, so no path tricks are required. Run npx iwsdk mcp inspect from the example to discover available tools and their CLI subcommands.
<JSON> is a JSON object string. Omit --input-json if no arguments are needed.{ok, workspaceRoot, operation, result}. Parse it to check assertions.--timeout 20000 for operations that may take longer (reload, xr enter, screenshot).IMPORTANT: Run each Bash command one at a time. Parse the JSON output and verify assertions before moving to the next command. Do NOT chain multiple CLI commands together.
IMPORTANT: When the instructions say "wait N seconds", use sleep N as a separate Bash command.
cd $IWSDK_REPO_ROOT/examples/physics && npm run fresh:install
Wait for this to complete before proceeding.
Start the dev server as a background task using the Bash tool's run_in_background: true parameter:
cd $IWSDK_REPO_ROOT/examples/physics && npm run dev
IMPORTANT: This command MUST be run with run_in_background: true on the Bash tool — do NOT append & to the command itself.
Once the background task is launched, poll the output for Vite's ready message (up to 60s). You can also run npx iwsdk dev status from the example directory until state.running becomes true. You do not need to extract or manage the port yourself; subsequent commands resolve the active runtime through the CLI automatically.
If the server fails to start within 60 seconds, report FAIL for all suites and skip to Step 5.
npx iwsdk ecs systems 2>/dev/null
This must return JSON with a list of systems. If it fails:
Run these commands in order:
npx iwsdk browser reload --timeout 20000 2>/dev/null
Then: sleep 3
npx iwsdk xr enter --timeout 20000 2>/dev/null
Then: sleep 2
npx iwsdk browser logs --input-json '{"count":20,"level":["error","warn"]}' 2>/dev/null
Assert: No error-level logs.
Find all physics bodies:
npx iwsdk ecs find --input-json '{"withComponents":["PhysicsBody"]}' 2>/dev/null
Assert: At least 1 entity.
For each entity found, query to identify dynamic vs static:
npx iwsdk ecs query --input-json '{"entityIndex":<N>,"components":["PhysicsBody"]}' 2>/dev/null
Check state field: "DYNAMIC" or "STATIC".
Save the dynamic entity as <sphere> and any static entity as <floor>.
Verify PhysicsSystem:
npx iwsdk ecs systems 2>/dev/null
Assert: PhysicsSystem at priority -2, physicsEntities count >= 1.
Test 1.1: Verify Dynamic Entity Exists
npx iwsdk ecs query --input-json '{"entityIndex":<sphere>,"components":["PhysicsBody","Transform"]}' 2>/dev/null
Assert:
state: "DYNAMIC"_engineBody: > 0 (Havok body created)gravityFactor: 1Note: By the time you query, the sphere may have already fallen and come to rest.
Test 1.2: Deterministic Gravity Test
Reset the sphere position, then use pause/step to observe fall:
npx iwsdk ecs pause 2>/dev/null
…
Plan IWSDK features, architecture, and code patterns with best-practice guidance.
Test XR session lifecycle and mode transitions to verify behavior and debug state issues.
Build, debug, and refine IWSDK PanelUI panels more efficiently.
Test multiple grab interaction modes with the iwsdk CLI.
Test XR interactions, panels, and audio behavior with the iwsdk CLI.
Find and click XR target objects to verify UI interactions work correctly.
Test slide, snap turn, teleport, and jump locomotion with iwsdk CLI.
Test level hierarchy, tags, and lighting setup with the iwsdk CLI.
Implement physics simulation, interactions, and collision debugging in IWSDK projects.
Test audio loading, playback, stop, and spatial audio via iwsdk CLI.
Test UI system behavior and compatibility against the poke example with iwsdk CLI.
Test environment settings and component schemas with iwsdk CLI against poke.