odoo-workspace
Skill2 starsChanged 3 months agoMITView on GitHub
Manage multiple Odoo environments, handle authentication, and switch between instances.
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-get-startedSkill
- 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
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 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.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
Initial Setup: If no instances are configured, use setup_instance to add the first one.
- Very specific: line 17
Discovery: Use list_instances to see which environments are currently configured.
- Very specific: line 22
Workflow: Use switch_instance to change the primary environment for a session.
≈ “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 Workspace Management
This skill provides the agent with the expertise required to manage multiple Odoo environments, handle authentication, and switch between instances.
Core Mandates
1. Multi-Instance Architecture
Brass-Monkey can manage multiple Odoo environments simultaneously. Each environment is identified by a unique instance_alias (e.g., "prod", "staging", "dev").
2. Configuration & Setup
- Initial Setup: If no instances are configured, use
setup_instanceto add the first one. You will need the Odoo URL, database name, username, and password/API key. - Verification:
setup_instanceautomatically validates credentials by attempting to authenticate. - Discovery: Use
list_instancesto see which environments are currently configured.
3. Session Defaults & Switching
- Default Instance: By default, tool calls use the first configured instance or the one set via
switch_instance. - Contextual Execution: You can override the default for any tool call by providing the
instance_aliasparameter. - Workflow: Use
switch_instanceto change the primary environment for a session. After switching, always callget_environmentto confirm the new context (User, DB, Version).
4. Cross-Instance Operations
You can move data between environments by reading from one instance and creating on another:
data = search_read(model: '...', instance_alias: 'prod')create_record(model: '...', values: data, instance_alias: 'staging')
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.

