About odoo-owl
odoo-owl is a skill for OWL frontend work in Odoo addons and standalone Owl applications. It directs implementation, integration, migration, testing, and debugging to references suited to the project’s detected OWL and Odoo versions.
Key features
- 01Detect the project's OWL and Odoo versions
- 02Build and modify OWL components
- 03Integrate with Odoo assets and web client
- 04Review and migrate field widgets
- 05Debug frontend behavior
- 06Test components, services, and registries
Use cases
- 01Implement an OWL component in an Odoo addon
- 02Check asset and template integration
- 03Plan an OWL version migration
- 04Investigate or test frontend issues
Install
Copy the command and run it in a terminal.
npx skills add https:/After installing, type/odoo-owlin Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
ASSETS.mdFIELD-WIDGETS.mdOWL-DEBUGGING.mdOWL3-CORE.mdOWL3-MIGRATION.mdOWL3-ODOO-INTEGRATION.mdOWL3-STATE-LIFECYCLE.mdOWL3-TEMPLATES.mdDetails
From the project READMEOdoo 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 and ASSETS.md.
- Build or review field widgets: use FIELD-WIDGETS.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: use OWL-DEBUGGING.md, compose with
odoodebugging workflow, and inspect browser/asset/test seams. - Test OWL components, widgets, services, and registries: compose with
odoo-web-testingand OWL-TESTING.md.
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.