Omi Me

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

Security Scan

The skill's files and runtime instructions match its stated purpose (an Omi.me CLI integration using an OMI API token); issues are implementation bugs and usability notes rather than evidence of misdirection or hidden exfiltration.

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.

Omi.me Integration for OpenClaw

Complete integration with Omi.me to sync and manage memories, action items (tasks), and conversations. Provides CLI tools.

Table of Contents

• Setup
• Token Management
• CLI Commands
  • Memories
  • Action Items / Tasks
  • Conversations
  • Sync
• Usage Examples

Setup

Automated Setup

# Run the setup script
bash /home/ubuntu/.openclaw/workspace/skills/omi-me/scripts/setup.sh

The setup script will:

1. Create config directory ~/.config/omi-me/
2. Guide you to configure your API token
3. Create symlinks for omi and omi-token commands

Manual Setup

# Create config directory
mkdir -p ~/.config/omi-me

# Save your API token
echo "omi_dev_your_token_here" > ~/.config/omi-me/token
chmod 600 ~/.config/omi-me/token

Get API Token

1. Visit https://docs.omi.me/doc/developer/api/overview
2. Generate a developer API key
3. Configure using:

# Interactive (recommended)
omi-token.sh set

# Or manually
echo "your-token" > ~/.config/omi-me/token

Token Management

omi-token.sh set    # Configure API token interactively
omi-token.sh get    # Print current token
omi-token.sh test   # Test connection to Omi.me

Token File

Default location: ~/.config/omi-me/token

You can also set via environment variable:

export OMI_API_TOKEN="your-token"

Files

• ~/.config/omi-me/token - API token storage

CLI Commands

Token Management

Command	Description
omi-token.sh set	Configure API token interactively
omi-token.sh get	Print current API token
omi-token.sh test	Test connection to Omi.me

Memories

Command	Description
omi memories list	List all memories
omi memories get <id>	Get specific memory
omi memories create "content"	Create new memory
omi memories create "content" --type preference	Create with type
omi memories update <id> "new content"	Update memory content
omi memories delete <id>	Delete a memory
omi memories search "query"	Search memories

Action Items / Tasks

Command	Description
omi tasks list	List all action items
omi tasks get <id>	Get specific task
omi tasks create "title"	Create new task
omi tasks create "title" --desc "description" --due "2024-01-15"	Create with details
omi tasks update <id> --title "new title"	Update task
omi tasks complete <id>	Mark as completed
omi tasks pending <id>	Mark as pending
omi tasks delete <id>	Delete a task

Conversations

Command	Description
omi conversations list	List all conversations
omi conversations get <id>	Get specific conversation
omi conversations create --title "My Chat" --participants "user1,user2"	Create conversation
omi conversations create --participants "user1,user2" --message "Hello!"	Create with initial message
omi conversations add-message <id> user "Hello world"	Add message to conversation
omi conversations delete <id>	Delete a conversation
omi conversations search "query"	Search conversations

Sync

Command	Description
omi sync memories	Sync memories from Omi.me
omi sync tasks	Sync action items from Omi.me
omi sync conversations	Sync conversations from Omi.me
omi sync all	Sync all data

Usage Examples

Token Configuration

Interactive setup:

omi-token.sh set

Test connection:

omi-token.sh test

Get current token:

omi-token.sh get

CLI Examples

List memories:

omi memories list

Create a memory:

omi memories create "Caio prefers working in English" --type preference

Create a task:

omi tasks create "Review Omi integration" --desc "Check if sync is working" --due "2024-02-01"

Mark task complete:

omi tasks complete <task-id>

Create conversation:

omi conversations create --title "Team Sync" --participants "alice,bob" --message "Let's discuss the project"

Add message:

omi conversations add-message <conv-id> user "I agree!"

Sync all data:

omi sync all

Rate Limits

Omi.me API rate limits:

• 100 requests per minute per API key
• 10,000 requests per day per user

The client automatically tracks rate limit headers and handles 429 responses.

Troubleshooting

"Token not configured"

# Configure interactively
omi-token.sh set

# Or check manually
cat ~/.config/omi-me/token

# If empty, add your token
echo "omi_dev_your_token" > ~/.config/omi-me/token

"Connection failed" or 401 error

# Test connection
omi-token.sh test

# Reconfigure if needed
omi-token.sh set

Permission denied for symlink

# Use full path instead
bash /home/ubuntu/.openclaw/workspace/skills/omi-me/scripts/omi-cli.sh memories list

---