[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CMHWB4QYMP88TDFARM3DQF":3,"skill-same:01M7CMHWB4QYMP88TDFARM3DQF":49},{"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":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7CMHWB4QYMP88TDFARM3DQF","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.","YYC-Cube\u002FYYC3-Knowledge-Base","YYC-Cube","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F235006543?v=4","01M79J2PH4SWD2X0825X6PN748","yyc3","01M79J2PHVK3F6ZBYT8K2SCZCW",1,"MIT","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fskills\u002Fodoo-migration-helper\u002FSKILL.md",[],[],"2026-11-15 14:19:17",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","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fskills\u002Fodoo-migration-helper",0,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base","https:\u002F\u002Fkb.yyc3.top\u002F","https:\u002F\u002Fgithub.com\u002FYYC-Cube","万象归元于云枢 | 深栈智启新纪元","2026-11-10 10:37:32",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill odoo-migration-helper",{"tool":41,"command":42},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill odoo-migration-helper",{"tool":44,"command":45},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill odoo-migration-helper","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fskills\u002Fodoo-migration-helper\u002FSKILL.md",true,[],[50,57,64,71,78,85],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M7CTDWHERCXPQCP0K03A86AS","vercel-sandbox","Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include \"Vercel Sandbox browser\", \"microVM Chrome\", \"agent-browser in sandbox\", \"browser automation on Vercel\", or any task requiring Chrome in a Vercel Sandbox.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fvercel-sandbox\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7CTD8D2BNJY54S65M47HEJA","slack","Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include \"check my Slack\", \"what channels have unreads\", \"send a message to\", \"search Slack for\", \"extract from Slack\", \"find who said\", or any task requiring programmatic Slack interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fslack\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7CTCSSB8ZP3Q58C3YZDZK1W","electron","Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include \"automate Slack app\", \"control VS Code\", \"interact with Discord app\", \"test this Electron app\", \"connect to desktop app\", or any task requiring automation of a native Electron application.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Felectron\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7CTCBJY76688V4DCZGWFHGQ","dogfood","Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to \"dogfood\", \"QA\", \"exploratory test\", \"find issues\", \"bug hunt\", \"test this app\u002Fsite\u002Fplatform\", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fdogfood\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7CTC4H0FFGVEAQR9PA4GA1A","agent-browser","Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to \"open a website\", \"fill out a form\", \"click a button\", \"take a screenshot\", \"scrape data from a page\", \"test this web app\", \"login to a site\", \"automate browser actions\", or any task requiring programmatic web interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fagent-browser\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7CTBKVFYBG78FDSABSDJTTQ","shadcn","Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn\u002Fui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for \"shadcn init\", \"create an app with --preset\", \"switch to --preset\", and for building a design system or applying a DESIGN.md or brand spec to shadcn\u002Fui.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-UI-界面组件\u002FYYC3-UI-界面组件-ui\u002Fskills\u002Fshadcn\u002FSKILL.md",[],[]]