Omi Integration

Sync recordings from Omi AI wearables (Omi, Limitless, etc.) via API and webhooks. Auto-sync transcripts, process recordings, and organize by device/date.

This skill implements the advertised sync/webhook features, but review these before installing or exposing it: - Required binaries mismatch: ensure you have python3 and ngrok installed in addition to curl and jq; the SKILL metadata omits python3/ngrok. - Secure your webhook: set OMI_WEBHOOK_SECRET before exposing the webhook (ngrok will make the endpoint public). Without a secret anyone can send events to your server. - Fix path traversal risk: the webhook handler uses recording IDs from incoming JSON to build filesystem paths without sanitization. If the webhook is reachable an attacker could craft a recording_id containing '../' or other segments to create/overwrite files outside the intended storage. Only run the server publicly after adding input validation or forcing canonical/safe filenames (strip or reject slashes, normalize and ensure paths remain under the storage directory). - Audit exposed behaviors: the server runs handler scripts with untrusted network input; check/limit what the handler does, and consider running the webhook server behind a firewall or proxy that restricts source IPs or requires authentication. - Missing or misleading docs: PROJECT.md mentions other scripts and registries not included in this package — be cautious that the repo metadata may reflect a larger project and not all components are bundled here. If you plan to use this skill: - Run it locally first, do not expose via ngrok until you set a webhook secret and verify that recording IDs are sanitized. - Consider running the webhook server under a dedicated, limited account or container to reduce blast radius. - If you cannot audit or patch the handler, do not expose the webhook publicly.

Type: OpenClaw Skill Name: omi-integration Version: 1.0.0 The skill implements a recording sync and real-time webhook system for Omi wearables, but exhibits high-risk behaviors including the automated setup of an ngrok tunnel (setup-ngrok.sh) and a background Python web server (webhook-server.py) that executes shell scripts. Furthermore, omi-webhook-handler.sh contains a path traversal vulnerability where it creates directories and writes files based on unvalidated recording_id fields from external webhook payloads, which could be exploited to write data outside the intended storage directory. While these features are aligned with the stated purpose of real-time integration, the combination of a public-facing tunnel and unvalidated file path construction presents a significant security risk.