[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73B34GY3Z38BS8JSX0ZDAR9":3,"skill-same:01M73B34GY3Z38BS8JSX0ZDAR9":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M73B34GY3Z38BS8JSX0ZDAR9","odoo-migration-helper",null,"Step-by-step guide for migrating Odoo custom modules between versions (v14→v15→v16→v17). Covers API changes, deprecated methods, and view migration.","kalash33\u002Fkstack","kalash33","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F90259149?v=4","01M7365X8Q0B73NYHA730SMZWN","Kalash Poddar","01M7365X9D0JK47C3Q0YCCK9Z2",0,"MIT","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fodoo-migration-helper\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: odoo-migration-helper\ndescription: \"Step-by-step guide for migrating Odoo custom modules between versions (v14→v15→v16→v17). Covers API changes, deprecated methods, and view migration.\"\nrisk: safe\nsource: \"self\"\n---\n\n# Odoo Migration Helper\n\n## Overview\n\nMigrating Odoo modules between major versions requires careful handling of API changes, deprecated methods, renamed fields, and new view syntax. This skill guides you through the migration process systematically, covering the most common breaking changes between versions.\n\n## When to Use This Skill\n\n- Upgrading a custom module from Odoo 14\u002F15\u002F16 to a newer version.\n- Getting a checklist of things to check before running `odoo-upgrade`.\n- Fixing deprecation warnings after a version upgrade.\n- Understanding what changed between two specific Odoo versions.\n\n## How It Works\n\n1. **Activate**: Mention `@odoo-migration-helper`, specify your source and target versions, and paste your module code.\n2. **Analyze**: Receive a list of breaking changes with before\u002Fafter code fixes.\n3. **Validate**: Get a migration checklist specific to your module's features.\n\n## Key Migration Changes by Version\n\n### Odoo 16 → 17\n\n| Topic | Old (v16) | New (v17) |\n|---|---|---|\n| View visibility | `attrs=\"{'invisible': [...]}\"` | `invisible=\"condition\"` |\n| Chatter | `\u003Cdiv class=\"oe_chatter\">` | `\u003Cchatter\u002F>` |\n| Required\u002FReadonly | `attrs=\"{'required': [...]}\"` | `required=\"condition\"` |\n| Python minimum | 3.10 | 3.10+ |\n| JS modules | Legacy `define(['web.core'])` | ES module `import` syntax |\n\n### Odoo 15 → 16\n\n| Topic | Old (v15) | New (v16) |\n|---|---|---|\n| Website published flag | `website_published = True` | `is_published = True` |\n| Mail aliases | `alias_domain` on company | Moved to `mail.alias.domain` model |\n| Report render | `_render_qweb_pdf()` | `_render_qweb_pdf()` (same, but signature changed) |\n| Accounting move | `account.move.line` grouping | Line aggregation rules updated |\n| Email threading | `mail_thread_id` | Deprecated; use `message_ids` |\n\n## Examples\n\n### Example 1: Migrate `attrs` visibility to Odoo 17\n\n```xml\n\u003C!-- v16 — domain-based attrs -->\n\u003Cfield name=\"discount\" attrs=\"{'invisible': [('product_type', '!=', 'service')]}\"\u002F>\n\u003Cfield name=\"discount\" attrs=\"{'required': [('state', '=', 'sale')]}\"\u002F>\n\n\u003C!-- v17 — inline Python expressions -->\n\u003Cfield name=\"discount\" invisible=\"product_type != 'service'\"\u002F>\n\u003Cfield name=\"discount\" required=\"state == 'sale'\"\u002F>\n```\n\n### Example 2: Migrate Chatter block\n\n```xml\n\u003C!-- v16 -->\n\u003Cdiv class=\"oe_chatter\">\n    \u003Cfield name=\"message_follower_ids\"\u002F>\n    \u003Cfield name=\"activity_ids\"\u002F>\n    \u003Cfield name=\"message_ids\"\u002F>\n\u003C\u002Fdiv>\n\n\u003C!-- v17 -->\n\u003Cchatter\u002F>\n```\n\n### Example 3: Migrate website_published flag (v15 → v16)\n\n```python\n# v15\nrecord.website_published = True\n\n# v16+\nrecord.is_published = True\n```\n\n## Best Practices\n\n- ✅ **Do:** Test with `--update=your_module` on each version before pushing to production.\n- ✅ **Do:** Use the official [Odoo Upgrade Guide](https:\u002F\u002Fupgrade.odoo.com\u002F) to get an automated pre-upgrade analysis report.\n- ✅ **Do:** Check OCA migration notes and the module's `HISTORY.rst` for community modules.\n- ✅ **Do:** Run `npm run validate` after migration to catch manifest or frontmatter issues early.\n- ❌ **Don't:** Skip intermediate versions — go v14→v15→v16→v17 sequentially; never jump.\n- ❌ **Don't:** Forget to update `version` in `__manifest__.py` (e.g., `17.0.1.0.0`).\n- ❌ **Don't:** Assume OCA modules are migration-ready; check their GitHub branch for the target version.\n\n## Limitations\n\n- Covers **v14 through v17** only — does not address v13 or older (pre-manifest era has fundamentally different module structure).\n- The **Odoo.sh automated upgrade** path has additional steps not covered here; refer to Odoo.sh documentation.\n- **Enterprise-specific modules** (e.g., `account_accountant`, `sign`) may have undocumented breaking changes; test on a staging environment with Enterprise license.\n- JavaScript OWL component migration (v15 Legacy → v16 OWL) is a complex topic not fully covered by this skill.\n","# Odoo Migration Helper\n\n## Overview\n\nMigrating Odoo modules between major versions requires careful handling of API changes, deprecated methods, renamed fields, and new view syntax. This skill guides you through the migration process systematically, covering the most common breaking changes between versions.\n\n## When to Use This Skill\n\n- Upgrading a custom module from Odoo 14\u002F15\u002F16 to a newer version.\n- Getting a checklist of things to check before running `odoo-upgrade`.\n- Fixing deprecation warnings after a version upgrade.\n- Understanding what changed between two specific Odoo versions.\n\n## How It Works\n\n1. **Activate**: Mention `@odoo-migration-helper`, specify your source and target versions, and paste your module code.\n2. **Analyze**: Receive a list of breaking changes with before\u002Fafter code fixes.\n3. **Validate**: Get a migration checklist specific to your module's features.\n\n## Key Migration Changes by Version\n\n### Odoo 16 → 17\n\n| Topic | Old (v16) | New (v17) |\n|---|---|---|\n| View visibility | `attrs=\"{'invisible': [...]}\"` | `invisible=\"condition\"` |\n| Chatter | `\u003Cdiv class=\"oe_chatter\">` | `\u003Cchatter\u002F>` |\n| Required\u002FReadonly | `attrs=\"{'required': [...]}\"` | `required=\"condition\"` |\n| Python minimum | 3.10 | 3.10+ |\n| JS modules | Legacy `define(['web.core'])` | ES module `import` syntax |\n\n### Odoo 15 → 16\n\n| Topic | Old (v15) | New (v16) |\n|---|---|---|\n| Website published flag | `website_published = True` | `is_published = True` |\n| Mail aliases | `alias_domain` on company | Moved to `mail.alias.domain` model |\n| Report render | `_render_qweb_pdf()` | `_render_qweb_pdf()` (same, but signature changed) |\n| Accounting move | `account.move.line` grouping | Line aggregation rules updated |\n| Email threading | `mail_thread_id` | Deprecated; use `message_ids` |\n\n## Examples\n\n### Example 1: Migrate `attrs` visibility to Odoo 17\n\n```xml\n\u003C!-- v16 — domain-based attrs -->\n\u003Cfield name=\"discount\" attrs=\"{'invisible': [('product_type', '!=', 'service')]}\"\u002F>\n\u003Cfield name=\"discount\" attrs=\"{'required': [('state', '=', 'sale')]}\"\u002F>\n\n\u003C!-- v17 — inline Python expressions -->\n\u003Cfield name=\"discount\" invisible=\"product_type != 'service'\"\u002F>\n\u003Cfield name=\"discount\" required=\"state == 'sale'\"\u002F>\n```\n\n### Example 2: Migrate Chatter block\n\n```xml\n\u003C!-- v16 -->\n\u003Cdiv class=\"oe_chatter\">\n    \u003Cfield name=\"message_follower_ids\"\u002F>\n    \u003Cfield name=\"activity_ids\"\u002F>\n    \u003Cfield name=\"message_ids\"\u002F>\n\u003C\u002Fdiv>\n\n\u003C!-- v17 -->\n\u003Cchatter\u002F>\n```\n\n### Example 3: Migrate website_published flag (v15 → v16)\n\n```python\n# v15\nrecord.website_published = True\n\n# v16+\nrecord.is_published = True\n```\n\n## Best Practices\n\n- ✅ **Do:** Test with `--update=your_module` on each version before pushing to production.\n- ✅ **Do:** Use the official [Odoo Upgrade Guide](https:\u002F\u002Fupgrade.odoo.com\u002F) to get an automated pre-upgrade analysis report.\n- ✅ **Do:** Check OCA migration notes and the module's `HISTORY.rst` for community modules.\n- ✅ **Do:** Run `npm run validate` after migration to catch manifest or frontmatter issues early.\n- ❌ **Don't:** Skip intermediate versions — go v14→v15→v16→v17 sequentially; never jump.\n- ❌ **Don't:** Forget to update `version` in `__manifest__.py` (e.g., `17.0.1.0.0`).\n- ❌ **Don't:** Assume OCA modules are migration-ready; check their GitHub branch for the target version.\n\n## Limitations\n\n- Covers **v14 through v17** only — does not address v13 or older (pre-manifest era has fundamentally different module structure).\n- The **Odoo.sh automated upgrade** path has additional steps not covered here; refer to Odoo.sh documentation.\n- **Enterprise-specific modules** (e.g., `account_accountant`, `sign`) may have undocumented breaking changes; test on a staging environment with Enterprise license.\n- JavaScript OWL component migration (v15 Legacy → v16 OWL) is a complex topic not fully covered by this skill.\n",{"name":5,"risk":24,"source":25,"description":7},"safe","self","main","b30820b3248f6676d5389f0ccabd4e5250c9c536","skills\u002Fodoo-migration-helper","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack","https:\u002F\u002Fgithub.com\u002Fkalash33","kalashpoddar.me","Tech-savvy Full Stack Developer 🚀 | Cybersecurity enthusiast 🔒 | Passionate about innovation and securing the digital world 🌐 | Let's code securely! 💻🔐","2026-05-20 04:11:22",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add kalash33\u002Fkstack --skill odoo-migration-helper",{"tool":40,"command":41},"bunx","bunx skills add kalash33\u002Fkstack --skill odoo-migration-helper",{"tool":43,"command":44},"pnpm","pnpm dlx skills add kalash33\u002Fkstack --skill odoo-migration-helper","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fodoo-migration-helper\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M73CFERCR43JCAP606E41EFB","zustand-store-ts","Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state\u002Faction separation. Use when building React state management, creating global stores, or implementing reacti...","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzustand-store-ts\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M73CFCMFVTAQEMTZ5HR10X8V","zoom-automation","Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-automation\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M73CFAA7EBWXJVXDQ1X555MB","zoho-crm-automation","Automate Zoho CRM tasks via Rube MCP (Composio): create\u002Fupdate records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzoho-crm-automation\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M73CF80XCM9K81567MJ8QZFW","zod-validation-expert","Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzod-validation-expert\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M73CF4YPMF3RA8ZJDXZSMD93","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M73CF2S25EN3XNAMKY47XHPS","zendesk-automation","Automate Zendesk tasks via Rube MCP (Composio): tickets, users, organizations, replies. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzendesk-automation\u002FSKILL.md",[],[]]