Odoo Manager

**Judgement:** This is a strong, technically solid Odoo integration skill designed around the official XML-RPC API, with robust context handling and generic ORM coverage. It’s well-suited for serious Odoo administration and integration tasks but carries high-impact risks if misused. **What it does well** - Connects to Odoo via XML-RPC using either password or API key. - Dynamically switches URL, database, and credentials using a clear precedence model (temporary_* for one-off operations, user_* for the session, env defaults as fallback). - Exposes generic execute_kw-based CRUD for any Odoo model, plus convenience flows for res.partner. - Supports model introspection (fields_get, ir.model, ir.model.fields), enabling dynamic and exploratory use. - Encourages good practices: explicit fields, pagination, and distinguishing connectivity/credential/business errors. **Risks / Limitations** - Can perform destructive operations (write, unlink) on any model, including production data, with no inherent guardrails or confirmation layers. - Misconfigured context (e.g., pointing to prod instead of staging) could lead to unintended modifications or deletions in critical environments. - Reliability and performance are bounded by the external Odoo server and network; no explicit retry or rate-limiting mechanisms are described. **Recommended usage scenarios** - Enterprise environments where an Odoo instance is available and you need programmatic access for integrations, admin tasks, or data syncs. - Technical users/admins familiar with Odoo domains and models who want a flexible, general-purpose ORM client rather than narrowly-scoped flows. - Cases where you must frequently switch between multiple Odoo environments (clients, staging, prod) and want explicit, inspectable context resolution. **Use with extra care** for bulk updates and deletions, and always verify that the current context (URL/DB/user) is the intended environment before executing write/unlink operations.