Robotics

What to consider before installing or using this skill: - Source provenance: the registry metadata lists no authoritative source here — verify the repository and author (LooperRobotics) on GitHub or another trusted host before installing or giving it network/credentials access. - Incomplete / stubbed behavior: many adapters and SLAM/navigation modules are stubs or placeholders (they set connected=True and return canned data). Treat this as development code. Expect runtime errors or missing functionality (e.g., some typing/import issues) if you try to use it as-is. - Credentials: the IM adapters accept secrets in their config (app_secret, access_token, corp_secret, etc.). Those are reasonable for an IM-integrated robot controller, but the skill currently does not declare or manage them — only pass them via config. Only provide credentials after inspecting the code and confirming network endpoints. - Hardware safety: before connecting this code to real robots, perform thorough review and testing in simulation or with the robot powered off/blocked. Mistakes in motion control or parsing can cause dangerous movement. Implement hardware-level safety interlocks. - Runtime bugs: there are small inconsistencies (example import name vs package, missing typing imports in some functions) which may cause runtime exceptions. Run tests in a safe environment and review error handling. - Recommended actions: verify the upstream repository/commit, run the test suite locally, review any code that would send network requests (the adapters are currently stubs), and only provide credentials/config through secure means if you trust the source. If you need autonomous operation, add careful authorization and safety checks before enabling control of physical robots.