Odoo Report Design

SkillDocs & knowledge

Designs and reviews Odoo QWeb HTML and PDF reports with stable layout, print-safe assets, paper formats, localization, and maintainable templates. Use when creating, redesigning, reviewing, or debugging Odoo reports, QWeb report templates, report CSS, headers, footers, tables, page breaks, or PDF rendering.

Use Odoo Report Design in Claude, ChatGPT or Ahel Desktop

Free. Sign in, add Odoo Report Design and connect your AI. About a minute.

Claude ChatGPT Ahel Desktop

Also: Claude Code · Cursor · Codex

Then ask your AI: use the Odoo Report Design skill

Details

Instructions available. Your AI can read the instructions. Execution depends on the setup they require.

Account requirements not reviewed. Check the skill instructions before use; Ahel provides instructions and does not run this skill.

No other account needed.

Add Ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.

Odoo Report DesignStart free

What this skill tells your AI

The instructions your AI receives, as published by mart337i/odoo-skills in skills/odoo-report-design/SKILL.md and read by Ahel’s review.

Use this skill for report presentation and rendering work. Compose it with the target version skill, odoo-website for shared QWeb/website concerns, odoo-web-testing for browser and asset verification, and odoo-migration for major-version ports.

First Move

Identify the target Odoo version, report action, model, template chain, paper format, external layout, report asset bundle, and any custom report value provider. Inspect the target version's parent templates and assets before choosing XPath anchors or CSS classes.

Workflow

Define the output contract: paper size, orientation, margins, header/footer, page numbering, languages, RTL requirements, expected page breaks, and whether HTML and PDF must match.
Separate data preparation from presentation. Keep business calculations in Python and use QWeb for composition, formatting, conditions, and iteration.
Build the smallest stable structure around the target version's supported report wrappers, external layout, and .page boundary.
Put report-only CSS and fonts in the target version's report asset bundle. Do not assume backend or website assets are available to PDF rendering.
Prefer semantic anchors and small inherited changes. Avoid copying core templates when an extension is sufficient.
Render representative records as HTML and PDF before calling the report complete.

Design Guardrails

Use escaped output by default: t-out for text and t-field for formatted model values. Treat rich HTML as an explicit, documented trust boundary.
Keep tables resilient to long names, translated labels, missing values, and multi-record output.
Prefer local, bundled assets and explicit print CSS over remote resources or browser-only behavior.
Treat paper dimensions, margins, DPI, fonts, and renderer availability as part of the design, not deployment details.
Preserve report access rules and data visibility while changing presentation.

References

REPORT-DESIGN.md - layout, QWeb, CSS, assets, and print constraints.
REPORT-REVIEW-CHECKLIST.md - implementation and review checklist.

Signals

GitHub stars: 40
Forks: 11
Last commit: Sep 2026

Advanced

Item type: skill
Key: odoo-report-design
Source: github.com/mart337i/odoo-skills

github.com/mart337i/odoo-skills