odoo-documents
Skill2 starsChanged 3 months agoMITView on GitHub
Functional expertise in Odoo's file management ecosystem, covering the foundational attachment layer and the advanced Document Management System.
In this repository30 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- odoo-attendanceSkill
- odoo-crmSkill
- odoo-dashboardsSkill
- odoo-data-opsSkill
- odoo-devSkill
- 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
- odoo-workspaceSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
Mandate: When creating or moving documents, always ensure they are assigned to the correct parent folder to maintain system-wide …
- Very specific: line 22
Validation: Use Odoo Activities (mail.activity) linked via request_activity_id to manage internal approval requests (e.g., "Validate this …
- Distinctive: line 24
Mandate: Do not bypass validation steps.
≈ “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 Documents & Attachments
This skill provides the agent with functional expertise in Odoo's file management ecosystem, covering the foundational attachment layer and the advanced Document Management System (DMS).
Core Mandates
1. Dual-Layer Architecture
Understand the distinction between the two layers of file management:
- Base Attachments (
ir.attachment): Foundational binary storage. Linked to records viares_modelandres_id. Use this for standard file storage on any record. - Managed Documents (
documents.document): The DMS layer. Provides workspaces, tags, and approval workflows. - Mandate (Odoo 18+): In newer versions, folders and workspaces are unified into the
documents.documentmodel. Check thetypefield ('binary', 'url', or 'folder').
2. Workspace & Folder Organization
- Hierarchy: Managed via
folder_id(pointing to anotherdocuments.documentin Odoo 18+). - Mandate: When creating or moving documents, always ensure they are assigned to the correct parent folder to maintain system-wide organization.
3. Workflows & Approvals
- Validation: Use Odoo Activities (
mail.activity) linked viarequest_activity_idto manage internal approval requests (e.g., "Validate this Vendor Bill"). - External Signatures: Documents requiring external signatures typically link to the Odoo Sign app.
- Mandate: Do not bypass validation steps. If a document has a pending approval activity, the agent must acknowledge it before executing further state changes.
4. Sharing & Permissions
- Internal Access: Controlled via
access_internal(view, edit, none) on the document. - Granular Sharing: Managed via the
documents.accessmodel, linking specific Documents to specific Partners. - Public Links: Controlled via
access_via_linkanddocument_token.
Available Resources
documents-logic.md: Deep-dive into Odoo 18 architectural changes, OCR/Action workflows, and attachment linking logic.documents-fields.json: Dense technical map of fields for Document, Attachment, Folder, and Access models.
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.

