odoo-reports
Skill2 starsChanged 3 months agoMITView on GitHub
Expertise required to discover, generate, and analyze Odoo business reports like Invoices, Quotations, and Packing Slips.
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-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, 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
Find: Use list_reports with a model (e.g., account.move) to find the technical report_name or id (e.g., account.report_invoice).
- Very specific: line 16
Execute: Use download_report with the report ID/name and the IDs of the records you want to print (e.g., [101]).
- Very specific: line 20
When downloading a report, provide a justification as part of the tool call.
≈ “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 Reports
This skill provides the agent with the expertise required to discover, generate, and analyze Odoo business reports (e.g., Invoices, Quotations, and Packing Slips).
Core Mandates
1. Report Architecture
Odoo reports are stored in the ir.actions.report model. They are typically rendered using the QWeb engine into PDF or HTML formats. Every report is linked to a specific business model (e.g., sale.order).
2. Workflow for Generating Reports
- Find: Use
list_reportswith amodel(e.g.,account.move) to find the technicalreport_nameorid(e.g.,account.report_invoice). - Execute: Use
download_reportwith the report ID/name and the IDs of the records you want to print (e.g.,[101]). - Analyze: Once the file is downloaded to the local workspace, use standard workspace tools (like
read_fileorpdf_to_text) to extract and analyze the content.
3. Contextual Rationale
When downloading a report, provide a justification as part of the tool call. This is particularly important for models that track "Printing" or "Sending" events (e.g., Odoo may automatically mark an invoice as "Sent" when it is rendered).
Note: Both report tools support the instance_alias parameter.
Available Resources
qweb-basics.md: Reference for Odoo's XML templating directives, which are used to construct report layouts.
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.

