Habitat-GS-Navigator

What to consider before installing and using this skill: - The skill is coherent with its description: it controls a local Habitat-GS bridge and uses hab-cli to navigate scenes. No credentials are requested. - The SKILL.md instructs you to git clone and pip install -e from a third‑party GitHub repo. That will run arbitrary code on your machine during install — review the repository contents (setup.py/pyproject, entry points, any scripts) before installing. - Prefer to install in an isolated environment (a dedicated conda env or virtualenv) or a disposable container, not as root or into your system Python, because habitat_sim and other native deps can be heavy and may require compilation. - Check the repo author and consider using an official release tag or checksum instead of cloning the main branch. If you cannot audit the code, run the service in a sandboxed VM or container. - Expect the skill to write episode logs under ~/.openclaw/workspace/memory/. If you have privacy concerns about local recordings or generated observations (the API returns base64 images), confirm what gets persisted and where. - If you plan to point the bridge at a remote host, be cautious: the CLI supports a --url / HABITAT_GS_BRIDGE_URL and could talk to remote servers; for normal use keep it on localhost. If you want a stronger safety posture: inspect the GitHub repository, prefer pinned releases, run the bridge in a container, and avoid installing into system Python environments.