ClawHub

Omi Me

v1.0.0

Complete Omi.me integration for memories, action items (tasks), and conversations. Full CRUD + sync capabilities for OpenClaw.

⭐ 4· 1.4k·0 current·0 all-time
by@caioiscoding
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name/description, required binaries (omi, omi-token), and required env var (OMI_API_TOKEN) align with the included CLI and token-management scripts. The scripts implement CRUD, search, and sync operations against the Omi.me API, which is what the skill advertises.
ℹ
Instruction Scope
SKILL.md instructs running the skill's setup script and interacting with the included CLI scripts; those scripts read/write only ~/.config/omi-me/token and call the Omi.me API. Two practical issues to be aware of: SKILL.md uses a hardcoded workspace path (/home/ubuntu/.openclaw/...) which may not match the user's environment, and the CLI has an implementation bug (omi-cli.sh defines OMI_API_URL but uses API_URL when composing requests) that will break API calls until fixed.
✓
Install Mechanism
This is instruction-only with bundled shell scripts; there is no external download of code or installation from third-party URLs. The setup script can create symlinks to /usr/local/bin and writes a small _meta.json for registration; these are local actions and visible in the code.
✓
Credentials
The only required secret is OMI_API_TOKEN (declared in metadata and used by the scripts). The scripts store the token in ~/.config/omi-me/token or accept it via environment, which is proportionate to the skill's functionality. No unrelated credentials or config paths are requested.
ℹ
Persistence & Privilege
The skill does not request always:true and does not modify other skills. The setup script will attempt to create symlinks in /usr/local/bin (may require elevated privileges) and write the token file and _meta.json into the skill directory — these are expected for a CLI integration but the symlink step can require user consent or sudo.
Assessment
This skill appears to be what it claims: a simple CLI wrapper for Omi.me that stores and uses your OMI_API_TOKEN. Before installing or running the setup script: 1) Inspect the scripts yourself (they are plain shell) and confirm you trust the omi.me endpoints. 2) Note the bug in omi-cli.sh: it sets OMI_API_URL but uses API_URL when making requests; API calls will fail until corrected (change ${API_URL} to ${OMI_API_URL}). 3) The setup script can create symlinks in /usr/local/bin — avoid running it with sudo unless you intend to make the commands globally available; without sudo the symlink step will be skipped. 4) The token is stored at ~/.config/omi-me/token (or read from OMI_API_TOKEN); treat that file like any other secret (chmod 600 is already used by the script). 5) Because the skill makes network calls to https://api.omi.me/v1/dev, verify the domain and your API key's permissions before granting access. If you want to be extra cautious, run commands manually (bash ./scripts/omi-token.sh set/test and bash ./scripts/omi-cli.sh ...) rather than creating global symlinks.

Like a lobster shell, security has layers — review code before you run it.

latestvk97bxvyaj5ata1dzteq46csfe980n87f

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Runtime requirements

🧠 Clawdis
Binsomi, omi-token
EnvOMI_API_TOKEN

Comments