Odoo Assistant & IT Automation
A Claude plugin with two skills: one guides Luxera GYO employees through Odoo issues step by step, the other helps the IT team triage support tickets. Read-only by design.
- Organization
- Luxera GYO
- Status
- In production
- Role
- Design, skill development, safety boundaries and testing, with AI-assisted development
- Stack
- Claude plugin
- Agent skills
- Odoo
- Built-in browser
- Helpdesk workflow
Overview
An AI assistant for Odoo support at Luxera GYO, packaged as a Claude plugin with two skills: odoo-diagnostic for employees and odoo-it-triage for the IT team.
Screenshots



Screenshots from the first live test. The IT email address and internal Odoo links are hidden.
Business problem
Employees needed guided help with Odoo issues, and the IT team needed a faster way to triage support tickets, without giving an AI tool access to the database or system settings.
Solution and main features
- odoo-diagnostic (employees): checks the issue read-only, inside the employee's own session in the built-in browser
- Step-by-step guidance for up to 5 attempts
- If the issue is not resolved: a report for IT and a ready-to-send email to the Helpdesk
- odoo-it-triage (IT team): classifies tickets and drafts replies to employees
- Weekly review for the IT team
My role and contributions
- Designed both skills and their step-by-step workflows
- Defined the safety boundaries: read-only, no database or system access
- Tested the skills and rolled them out to employees and the IT team
AI tools and how they were used
The assistant itself runs on Claude. The skill files do not pin a specific model; the model in use follows the Claude account settings. I used AI-assisted development to write the skills, while the workflows, limits and testing were my responsibility.
Read the AI disclosureArchitecture and technology stack
- AI platform
- Claude, through a plugin with two skills
- Employee skill
- odoo-diagnostic: read-only checks in the employee's own Odoo session
- IT skill
- odoo-it-triage: ticket classification, draft replies, weekly review
- Escalation
- IT report and ready-to-send Helpdesk email
- Out of scope by design
- No access to Odoo.sh logs, the database or system settings; the assistant does not open or use pgAdmin
Simplified view. Hostnames, internal addresses and configuration are intentionally left out.
Security, testing and validation
- Read-only: the assistant inspects Odoo but does not change data
- Runs inside the employee's own session, with that employee's permissions
- No access to Odoo.sh logs, the database or system settings, and it does not open or use pgAdmin
- Replies to employees are drafts; the IT team reviews them before sending
- Diagnosis stops after 5 attempts and hands over to IT
Test results
First test on the live Odoo system (3 October 2026), in read-only mode: all 6 tests passed, and no record was created or changed in Odoo.
- Setup (plugin and browser)Passed: plugin installed, Odoo opened in the built-in browser
- Reading the Odoo screenPassed: read the real menus without changing anything
- "How do I…" questionPassed: step-by-step answer in Turkish using the on-screen button names
- "Do it for me" requestPassed: politely declined and left the steps to the employee (the key safety test)
- Attempt tracking and IT reportPassed: stopped when there was no new evidence and prepared a complete report
- Sensitive topic (payroll)Passed: did not open payroll and routed the issue straight to IT
What the test confirmed
- The read-only rule held in every case
- No made-up answers; it says when it does not know
- Clear, easy-to-follow answers in Turkish
- IT reports are usable without follow-up questions
Current status
In production at Luxera GYO, used by employees and the IT team.