Odoo owl
Odoo OWL frontend engineering guidance covering components, templates, reactivity, hooks, props, plugins, registries, debugging, assets, and OWL 1/2/3 migration. Use when working with Odoo frontend components, @odoo/owl, static/src JavaScript/XML templates, signals, proxy, props, t-on, t-ref, t-model, registries, plugins, or OWL migrations.From its SKILL.md
npx -y skills add mart337i/odoo-skills --skill odoo-owlAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 21 stars21 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.0 KB, 419 tokens by cl100k_base, as published. Nobody here has run it
Odoo OWL
Use this skill for OWL frontend work in Odoo addons or standalone Owl applications.
First Move
Do not assume OWL 3. First detect the actual OWL/Odoo frontend version from local source and project code:
- Odoo version from branch, manifests, docs, or config.
- Local OWL source under
$ODOO_SOURCEwhen set, especiallyaddons/web/static/lib/owlor equivalent. - Existing imports from
@odoo/owl,owl,@web/*, and local frontend conventions. - Asset declarations in
__manifest__.pyand existingstatic/src/js,static/src/xml, andstatic/src/scsspatterns.
Use the OWL 3 references only when the target project actually uses OWL 3. For older Odoo versions, local source and existing project conventions supersede this skill's OWL 3 notes.
Route The Task
- Build or change OWL components: use OWL3-CORE.md, OWL3-TEMPLATES.md, and OWL3-STATE-LIFECYCLE.md.
- Integrate with Odoo assets/web client: use OWL3-ODOO-INTEGRATION.md.
- Migrate OWL 1/2 code toward OWL 3: use OWL3-MIGRATION.md, but verify local compatibility first.
- Review frontend guideline/style concerns: compose with
odoo-code-review. - Debug broken Odoo frontend behavior: compose with
odoodebugging workflow and inspect browser/asset/test seams.
Always Apply
Keep UI state explicit and reactive. Prefer small components with clear props and events. Avoid mutating props. Clean up listeners and external resources with lifecycle hooks. Treat unsafe HTML as a security boundary. Verify asset bundle registration and template loading before blaming OWL behavior.
What ships with it: 5 files
19.1 KB alongside SKILL.md
- OWL3-CORE.md3.5 KB
- OWL3-MIGRATION.md4.5 KB
- OWL3-ODOO-INTEGRATION.md3.5 KB
- OWL3-STATE-LIFECYCLE.md4.0 KB
- OWL3-TEMPLATES.md3.5 KB