odoo-js

Migrate legacy Odoo widgets to OWL 2 across v17–v19.

1|1|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/halim-23/odoo-dev-plugin --skill odoo-js
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: odoo-js
Source: https://github.com/halim-23/odoo-dev-plugin/tree/main/skills/odoo-js
Command: npx skills add https://github.com/halim-23/odoo-dev-plugin --skill odoo-js

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides expert guidance on building Odoo frontend components with OWL, focusing on migration from legacy widgets to OWL 2 and across v17–v19 CE/EE to help teams modernize the UI and adopt best practices.

Core Features & Use Cases

  • OWL 2 migration patterns and deprecation handling for legacy Backbone-based widgets.
  • Creating and integrating custom field widgets, view widgets, and client actions within Odoo web interfaces.
  • Patching, extension, and view customization workflows (forms, lists, kanban) using the registry APIs and new module system.

Quick Start

Explain how to migrate an existing Odoo frontend widget to OWL 2 and implement a new OWL component.

Frequently Asked Questions about odoo-js

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate legacy Odoo widgets to OWL 2?

Migrate legacy Odoo widgets to OWL 2 by adopting the new module system with /** @odoo-module **/ directives, replacing Backbone patterns with OWL components, and using registry APIs for integration across v17–v19.

How do I create custom field widgets and client actions in Odoo OWL?

Create custom field widgets and client actions in Odoo OWL by registering components explicitly within registry categories and safely integrating services like orm, dialog, and action inside your OWL components.

Does Odoo OWL work with the new ES module system across versions 17 to 19?

Yes, Odoo OWL works across versions 17 to 19 by enforcing ES module usage with /** @odoo-module **/ directives, explicit registry categories, and event directives for modern frontend component development.

What is the best way to patch and customize Odoo views using OWL?

Patch and customize Odoo views using OWL by applying patching strategies and extension workflows with registry APIs in Form, List, and Kanban contexts to safely modify view widgets.

Why do I need explicit registry categories for Odoo OWL components?

Explicit registry categories are required for Odoo OWL components to ensure safe integration of services like orm, dialog, and action, and to maintain proper structure within the new ES module system.

Can I integrate orm, dialog, and action services inside Odoo OWL components?

Yes, you can integrate orm, dialog, and action services inside Odoo OWL components by following safe integration best practices enforced by the new module system and registry APIs.