Odoo Assistant Store Manager

Odoo ERP via XML-RPC — sales, web orders, stock, products (CLI). Optional Discuss listener.

Security Scan

The skill largely does what it claims (an XML-RPC Odoo CLI and optional Discuss listener) but there are inconsistencies in the registry metadata and a non-trivial surface for remote fetching / listener-driven actions (SSRF and runtime command execution) that warrant caution.

Purpose & Capability

The code and environment variables in skill.json / README match the stated purpose (Odoo XML-RPC operations). However the registry metadata provided to you earlier claims no required env vars and the SKILL.md calls this 'instruction-only' despite two substantial Python modules being included; those mismatches are incoherent and should be fixed in the registry before publishing.

Instruction Scope

SKILL.md instructs the agent to run local scripts and only run the optional listener on explicit request, which is appropriate. The listener (src/odoo_listener.py) fetches arbitrary URLs (requests / urllib) and scrapes HTML, and it constructs and runs odoo_manager commands based on Discuss messages. This enables server-side fetching of attacker-controlled URLs (SSRF / internal-network probing) and causes the runtime to execute manager commands derived from external input. While subprocess is invoked without a shell (reducing classic shell-injection), arguments from untrusted messages can still trigger operations (e.g., downloading images, contacting arbitrary endpoints or performing updates).

Install Mechanism

No install spec is provided (lowest install risk). requirements.txt contains only 'requests', which is consistent with the listener. There is no external archive download or unknown install host.

Credentials

The required environment variables in skill.json (ODOO_URL, ODOO_DB, ODOO_USER, ODOO_PASSWORD) are appropriate and expected for an Odoo integration. The inconsistency is that the registry metadata shown to you earlier listed 'Required env vars: none' — that mismatch is a red flag for publishing/metadata hygiene and could lead to accidental deployment without needed secrets or with defaults. Optional vars (BOT partner id, category IDs) are reasonable.

Persistence & Privilege

The skill does not request 'always: true' and will not be force-included. The only higher-privilege behavior is the optional long-running listener, which the SKILL.md and README explicitly mark as 'privileged' and say to run only if requested. Because the listener polls Odoo and can run manager commands autonomously when enabled, it increases blast radius if activated—so it should be started only with deliberate user consent and in controlled environments.

What to consider before installing

This skill appears to implement an Odoo CLI and an optional Discuss listener; functionally coherent but exercise caution before enabling the listener. Before installing or running: 1) Fix the metadata mismatch — ensure the registry lists the required env vars (ODOO_URL/DB/USER/PASSWORD) so you don’t accidentally publish or run without secrets configured. 2) Do NOT run the listener in production unless you explicitly want a long‑running bot that polls Odoo Discuss; test it in a staging environment first. 3) Consider network controls for the runtime ( e.g., block requests to internal IP ranges / metadata endpoints ) because the skill will fetch URLs supplied via messages or product fields (SSRF risk). 4) Run with least-privilege Odoo credentials (avoid admin/root DB user) and rotate keys if re-used. 5) Review the full code locally (already included) and run tests in an isolated environment. If you don’t need automated polling and external-URL scraping, use only the CLI (odoo_manager.py) and avoid setting ODOO_BOT_PARTNER_ID.

Use the terminal to run src/odoo_manager.py from the skill root (the directory that contains this file).

Path

• From the skill root: python3 src/odoo_manager.py …
• From anywhere: use the absolute path to src/odoo_manager.py.

Commands

Sales & POS summary / web backlog

python3 src/odoo_manager.py check_sales
python3 src/odoo_manager.py web_orders

Stock search / update

python3 src/odoo_manager.py check_stock --query "NAME OR BARCODE"
python3 src/odoo_manager.py update_stock --ref "NAME OR BARCODE" --qty 10

(--ref, --barcode, and --name are accepted as aliases for the product reference on update_stock.)

Top sales

python3 src/odoo_manager.py top_sales --period mes

Add product

python3 src/odoo_manager.py add_product --name "…" --price 9.95 --qty 5 \
  --barcode "EAN" --category "keyword" --min_age "8" --players "2-4" --time "30" \
  --description "HTML …" --image-url "https://…"

See README.md for environment variables and Odoo-specific IDs (ODOO_TAX_ID, stock location, category maps).

Order / event helpers

python3 src/odoo_manager.py get_order_details --name "S00123"
python3 src/odoo_manager.py get_event_registrations --name "Event name"

Rules for the agent

1. Run the script for Odoo operations; do not invent API results.
2. Summarize terminal output clearly for the user.
3. On errors, show the message. Tell the user to verify ODOO_URL, ODOO_DB, ODOO_USER, and ODOO_PASS or ODOO_PASSWORD in their environment. Do not create, edit, or “fix” .env or secret files unless the user explicitly asks to change a named file or variable.
4. Optional listener: src/odoo_listener.py polls Odoo Discuss and runs CLI commands. Long-running, privileged. Only run if the user requests it; requires ODOO_BOT_PARTNER_ID. See README.md.

Human setup

The installer sets the variables listed in skill.json / README.md. To keep command snippets handy, users may manually copy examples into their own notes. This skill does not require editing workspace identity files (SOUL.md, TOOLS.md, etc.).