Omie ERP

Omie ERP integration via API. Manage clients, products, orders, invoices (NF-e), financials (contas a receber/pagar), and stock. Use when users ask about ERP...

This skill appears to implement the advertised Omie ERP API client and a simple webhook receiver, and the Python source is readable. Before installing: 1) Provide OMIE_APP_KEY and OMIE_APP_SECRET in your environment — the registry metadata omitted these but they are required. 2) Note the SKILL.md examples sometimes reference slightly different paths (e.g., skills/omie/scripts vs. scripts/) — verify file placement when invoking. 3) The webhook defaults to 0.0.0.0: if you run it, consider binding to localhost or putting it behind an authenticated, TLS-terminating proxy (or firewall) so sensitive invoice/customer events aren't exposed. 4) The webhook logs full payloads to stderr; ensure logs are stored/handled per your data-protection policies because they may include personally identifiable or financial data. 5) If you need higher assurance, inspect the included Python files yourself (they are short and straightforward) and update the registry metadata to declare the required environment variables before using the skill in production.

Type: OpenClaw Skill Name: omie Version: 1.0.3 The OpenClaw skill 'omie' is a benign integration with the Omie ERP system. It securely handles API keys via environment variables and communicates with the legitimate, hardcoded Omie API endpoint. The `omie_client.py` script parses command-line arguments as data for JSON payloads, mitigating shell injection risks, and the `omie_webhook.py` script simply receives and logs webhook data locally without executing arbitrary code. There is no evidence of data exfiltration, unauthorized command execution, persistence mechanisms, or prompt injection attempts in any of the provided files.