odoo-get-started
Skill2 starsChanged 3 months agoMITView on GitHub
MANDATORY FIRST STEP. Orientation skill to establish the Odoo World Map context (Version, Apps, Company, Permissions) BEFORE executing any other tools.
In this repository30 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- odoo-attendanceSkill
- odoo-crmSkill
- odoo-dashboardsSkill
- odoo-data-opsSkill
- odoo-devSkill
- odoo-documentsSkill
- odoo-field-serviceSkill
- odoo-financeSkill
- odoo-frontdeskSkill
- odoo-helpdeskSkill
- odoo-hrSkill
- odoo-introspectorSkill
- odoo-inventorySkill
- odoo-knowledgeSkill
- odoo-mrpSkill
- odoo-plmSkill
- odoo-productsSkill
- odoo-projectsSkill
- odoo-purchasingSkill
- odoo-qualitySkill
- odoo-relationsSkill
- odoo-reportsSkill
- odoo-salesSkill
- odoo-securitySkill
- odoo-spreadsheetsSkill
- odoo-uxSkill
- odoo-websiteSkill
- odoo-worksheetsSkill
- odoo-workspaceSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 0 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Enforcement: Do NOT attempt search_read, list_models, or any business logic until get_environment has returned.
- Very specific: line 17
When you receive the get_environment response, you must internalize:
- Very specific: line 28
Basic Context: Run get_environment() for standard tasks.
- Very specific: line 29
Security Context: If the task involves permissions or access troubleshooting, run get_environment(show_security: true).
- Very specific: line 30
Capability Context: If you are unsure what business processes are supported, run get_environment(show_manifest: true).
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Skill: Odoo Orientation (The Mandatory Start)
This skill ensures the agent establishes a comprehensive "World Map" of the Odoo environment immediately upon session start or when switching instances. Bypassing this step is a violation of project architecture.
Core Mandates
1. The "World Map" Protocol (NON-NEGOTIABLE)
- Mandate: Your ABSOLUTE FIRST action when starting a task in a new or unknown Odoo instance MUST be to call
get_environment. - Enforcement: Do NOT attempt
search_read,list_models, or any business logic untilget_environmenthas returned. - Reasoning: Odoo environments vary wildly by version, installed apps, and company structures. Starting "blind" leads to "hallucinated" field names and inefficient tool-chaining.
2. Interpreting the Environment & Company Context
When you receive the get_environment response, you must internalize:
- Version: Are you on Odoo v18 (current) or an older legacy version? (Methods and fields change between versions).
- User Context: What is your name and login? (Used for audit trails).
- Active Context (
active_context):- Programmatic Scope: View the root
active_contextpayload to see yourimplicit_allowed_company_ids. - Implicit Injection: Brass-Monkey automatically injects these company IDs into every query. You have global read visibility across all of them by default. Check the
multi_companyflag inactive_context— many instances are single-company, where company filtering is unnecessary. - Restricting Scope: On multi-company instances, to target a single organization do not alter user settings — apply an explicit domain filter on models that have a
company_idfield, e.g.,[['company_id', '=', ID]].
- Programmatic Scope: View the root
- Organization: How many companies exist? Which one is active? What are the local currencies and languages?
- Apps Manifest: (If
show_manifest: true) What modules are installed? (e.g., ifcrmis not installed, do not attempt to search for leads).
3. Progressive Disclosure
- Basic Context: Run
get_environment()for standard tasks. - Security Context: If the task involves permissions or access troubleshooting, run
get_environment(show_security: true). - Capability Context: If you are unsure what business processes are supported, run
get_environment(show_manifest: true).
Workflow Example
- Connect: User asks to create a sale order.
- Orient: Call
get_environment(). - Analyze: "I am logged in as 'Admin' on Odoo v18. 'Sale Management' is installed. Active company is 'MyCompany' (USD)."
- Execute: Proceed with
search_readorinspect_modelwith confidence.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

