[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C2K0RAMQJ07B2ZRYD242H0":3,"skill-same:01M7C2K0RAMQJ07B2ZRYD242H0":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},"01M7C2K0RAMQJ07B2ZRYD242H0","odoo-upgrade-advisor",null,"Step-by-step Odoo version upgrade advisor: pre-upgrade checklist, community vs enterprise upgrade path, OCA module compatibility, and post-upgrade validation.","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\u002Fplugins\u002Fantigravity-awesome-skills-claude\u002Fskills\u002Fodoo-upgrade-advisor\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: odoo-upgrade-advisor\ndescription: \"Step-by-step Odoo version upgrade advisor: pre-upgrade checklist, community vs enterprise upgrade path, OCA module compatibility, and post-upgrade validation.\"\nrisk: safe\nsource: \"self\"\n---\n\n# Odoo Upgrade Advisor\n\n## Overview\n\nUpgrading Odoo between major versions (e.g., v15 → v16 → v17) requires careful preparation, testing, and validation. This skill provides a structured pre-upgrade checklist, guides you through the upgrade tools (Odoo Upgrade Service and OpenUpgrade), and gives you a post-upgrade validation protocol.\n\n## When to Use This Skill\n\n- Planning a major Odoo version upgrade.\n- Identifying which custom modules need to be migrated.\n- Running the upgrade on a staging environment before production.\n- Validating the system after an upgrade.\n\n## How It Works\n\n1. **Activate**: Mention `@odoo-upgrade-advisor`, state your current and target version.\n2. **Plan**: Receive the full upgrade roadmap and risk assessment.\n3. **Execute**: Get a step-by-step upgrade command sequence.\n\n## Upgrade Paths\n\n| From | To | Supported? | Tool |\n|---|---|---|---|\n| v16 | v17 | ✅ Direct | Odoo Upgrade Service \u002F OpenUpgrade |\n| v15 | v16 | ✅ Direct | Odoo Upgrade Service \u002F OpenUpgrade |\n| v14 | v15 | ✅ Direct | Odoo Upgrade Service \u002F OpenUpgrade |\n| v14 | v17 | ⚠️ Multi-hop | v14→v15→v16→v17 (cannot skip) |\n| v13 or older | any | ❌ Not supported | Manual migration required |\n\n## Examples\n\n### Example 1: Pre-Upgrade Checklist\n\n```text\nBEFORE YOU START:\n  ☑ 1. List all installed modules (Settings → Technical → Modules)\n        Export to CSV and review for custom\u002FOCA modules\n  ☑ 2. Check OCA compatibility matrix for each community module\n        https:\u002F\u002Fgithub.com\u002FOCA\u002Fmaintainer-tools\u002Fwiki\u002FMigration-Status\n  ☑ 3. Take a full backup (database + filestore) — your restore point\n  ☑ 4. Clone production to a staging environment\n  ☑ 5. Run the Odoo Upgrade pre-analysis:\n        https:\u002F\u002Fupgrade.odoo.com\u002F → Upload DB → Review breaking changes report\n  ☑ 6. Review custom modules against migration notes\n        (use @odoo-migration-helper for per-module analysis)\n  ☑ 7. Upgrade and test in staging → Fix all errors → Re-test\n  ☑ 8. Schedule a production maintenance window\n  ☑ 9. Notify users of scheduled downtime\n  ☑ 10. Perform production upgrade → Validate → Go\u002FNo-Go decision\n```\n\n### Example 2: Community Upgrade with OpenUpgrade\n\n```bash\n# Clone OpenUpgrade for the TARGET version (e.g., upgrading to v17)\ngit clone https:\u002F\u002Fgithub.com\u002FOCA\u002FOpenUpgrade.git \\\n  --branch 17.0 \\\n  --single-branch \\\n  \u002Fopt\u002Fopenupgrade\n\n# Run the migration against your staging database\npython3 \u002Fopt\u002Fopenupgrade\u002Fodoo-bin \\\n  --update all \\\n  --database odoo_staging \\\n  --config \u002Fetc\u002Fodoo\u002Fodoo.conf \\\n  --stop-after-init \\\n  --load openupgrade_framework\n\n# Review the log for errors before touching production\ntail -200 \u002Fvar\u002Flog\u002Fodoo\u002Fodoo.log | grep -E \"ERROR|WARNING|Traceback\"\n```\n\n### Example 3: Post-Upgrade Validation Checklist\n\n```text\nAfter upgrading, validate these critical areas before going live:\n\nAccounting:\n  ☑ Trial Balance totals match the pre-upgrade snapshot\n  ☑ Open invoices, bills, and payments are accessible\n  ☑ Bank reconciliation can be performed on a test statement\n\nInventory:\n  ☑ Stock valuation report matches pre-upgrade (run Inventory Valuation)\n  ☑ Open Purchase Orders and Sale Orders are visible\n\nHR \u002F Payroll:\n  ☑ All employee records are intact\n  ☑ Payslips from the last 3 months are accessible and correct\n\nCustom Modules:\n  ☑ Every custom module loaded without ImportError or XML error\n  ☑ Run the critical business workflows end-to-end:\n      Create sale order → confirm → deliver → invoice → payment\n\nUsers & Security:\n  ☑ User logins work correctly\n  ☑ Access rights are preserved (spot-check 3-5 users)\n```\n\n## Best Practices\n\n- ✅ **Do:** Always upgrade on a **copy of production** (staging) first — never the live instance.\n- ✅ **Do:** Keep the old version running until the new version is **fully validated and signed off**.\n- ✅ **Do:** Check OCA's migration status page: [OCA Migration Status](https:\u002F\u002Fgithub.com\u002FOCA\u002Fmaintainer-tools\u002Fwiki\u002FMigration-Status)\n- ✅ **Do:** Use the [Odoo Upgrade Service](https:\u002F\u002Fupgrade.odoo.com\u002F) pre-analysis report to get a list of breaking changes **before writing any code**.\n- ❌ **Don't:** Skip intermediate versions — Odoo requires sequential upgrades (v14→v15→v16→v17).\n- ❌ **Don't:** Upgrade custom modules and Odoo core simultaneously — adapt Odoo core first, then fix custom modules.\n- ❌ **Don't:** Run OpenUpgrade against production directly — always test on a staging copy first.\n\n## Limitations\n\n- Covers **v14–v17** only. Versions v13 and older have a fundamentally different module structure and require manual migration.\n- **Enterprise-exclusive module changes** (e.g., `sign`, `account_accountant`) may have undocumented breaking changes not included in OpenUpgrade.\n- The **Odoo.sh** automated upgrade path has a separate workflow (managed from the Odoo.sh dashboard) not covered here.\n- OWL JavaScript component migration (legacy widget → OWL v16+) is a complex front-end topic beyond the scope of this skill.\n","# Odoo Upgrade Advisor\n\n## Overview\n\nUpgrading Odoo between major versions (e.g., v15 → v16 → v17) requires careful preparation, testing, and validation. This skill provides a structured pre-upgrade checklist, guides you through the upgrade tools (Odoo Upgrade Service and OpenUpgrade), and gives you a post-upgrade validation protocol.\n\n## When to Use This Skill\n\n- Planning a major Odoo version upgrade.\n- Identifying which custom modules need to be migrated.\n- Running the upgrade on a staging environment before production.\n- Validating the system after an upgrade.\n\n## How It Works\n\n1. **Activate**: Mention `@odoo-upgrade-advisor`, state your current and target version.\n2. **Plan**: Receive the full upgrade roadmap and risk assessment.\n3. **Execute**: Get a step-by-step upgrade command sequence.\n\n## Upgrade Paths\n\n| From | To | Supported? | Tool |\n|---|---|---|---|\n| v16 | v17 | ✅ Direct | Odoo Upgrade Service \u002F OpenUpgrade |\n| v15 | v16 | ✅ Direct | Odoo Upgrade Service \u002F OpenUpgrade |\n| v14 | v15 | ✅ Direct | Odoo Upgrade Service \u002F OpenUpgrade |\n| v14 | v17 | ⚠️ Multi-hop | v14→v15→v16→v17 (cannot skip) |\n| v13 or older | any | ❌ Not supported | Manual migration required |\n\n## Examples\n\n### Example 1: Pre-Upgrade Checklist\n\n```text\nBEFORE YOU START:\n  ☑ 1. List all installed modules (Settings → Technical → Modules)\n        Export to CSV and review for custom\u002FOCA modules\n  ☑ 2. Check OCA compatibility matrix for each community module\n        https:\u002F\u002Fgithub.com\u002FOCA\u002Fmaintainer-tools\u002Fwiki\u002FMigration-Status\n  ☑ 3. Take a full backup (database + filestore) — your restore point\n  ☑ 4. Clone production to a staging environment\n  ☑ 5. Run the Odoo Upgrade pre-analysis:\n        https:\u002F\u002Fupgrade.odoo.com\u002F → Upload DB → Review breaking changes report\n  ☑ 6. Review custom modules against migration notes\n        (use @odoo-migration-helper for per-module analysis)\n  ☑ 7. Upgrade and test in staging → Fix all errors → Re-test\n  ☑ 8. Schedule a production maintenance window\n  ☑ 9. Notify users of scheduled downtime\n  ☑ 10. Perform production upgrade → Validate → Go\u002FNo-Go decision\n```\n\n### Example 2: Community Upgrade with OpenUpgrade\n\n```bash\n# Clone OpenUpgrade for the TARGET version (e.g., upgrading to v17)\ngit clone https:\u002F\u002Fgithub.com\u002FOCA\u002FOpenUpgrade.git \\\n  --branch 17.0 \\\n  --single-branch \\\n  \u002Fopt\u002Fopenupgrade\n\n# Run the migration against your staging database\npython3 \u002Fopt\u002Fopenupgrade\u002Fodoo-bin \\\n  --update all \\\n  --database odoo_staging \\\n  --config \u002Fetc\u002Fodoo\u002Fodoo.conf \\\n  --stop-after-init \\\n  --load openupgrade_framework\n\n# Review the log for errors before touching production\ntail -200 \u002Fvar\u002Flog\u002Fodoo\u002Fodoo.log | grep -E \"ERROR|WARNING|Traceback\"\n```\n\n### Example 3: Post-Upgrade Validation Checklist\n\n```text\nAfter upgrading, validate these critical areas before going live:\n\nAccounting:\n  ☑ Trial Balance totals match the pre-upgrade snapshot\n  ☑ Open invoices, bills, and payments are accessible\n  ☑ Bank reconciliation can be performed on a test statement\n\nInventory:\n  ☑ Stock valuation report matches pre-upgrade (run Inventory Valuation)\n  ☑ Open Purchase Orders and Sale Orders are visible\n\nHR \u002F Payroll:\n  ☑ All employee records are intact\n  ☑ Payslips from the last 3 months are accessible and correct\n\nCustom Modules:\n  ☑ Every custom module loaded without ImportError or XML error\n  ☑ Run the critical business workflows end-to-end:\n      Create sale order → confirm → deliver → invoice → payment\n\nUsers & Security:\n  ☑ User logins work correctly\n  ☑ Access rights are preserved (spot-check 3-5 users)\n```\n\n## Best Practices\n\n- ✅ **Do:** Always upgrade on a **copy of production** (staging) first — never the live instance.\n- ✅ **Do:** Keep the old version running until the new version is **fully validated and signed off**.\n- ✅ **Do:** Check OCA's migration status page: [OCA Migration Status](https:\u002F\u002Fgithub.com\u002FOCA\u002Fmaintainer-tools\u002Fwiki\u002FMigration-Status)\n- ✅ **Do:** Use the [Odoo Upgrade Service](https:\u002F\u002Fupgrade.odoo.com\u002F) pre-analysis report to get a list of breaking changes **before writing any code**.\n- ❌ **Don't:** Skip intermediate versions — Odoo requires sequential upgrades (v14→v15→v16→v17).\n- ❌ **Don't:** Upgrade custom modules and Odoo core simultaneously — adapt Odoo core first, then fix custom modules.\n- ❌ **Don't:** Run OpenUpgrade against production directly — always test on a staging copy first.\n\n## Limitations\n\n- Covers **v14–v17** only. Versions v13 and older have a fundamentally different module structure and require manual migration.\n- **Enterprise-exclusive module changes** (e.g., `sign`, `account_accountant`) may have undocumented breaking changes not included in OpenUpgrade.\n- The **Odoo.sh** automated upgrade path has a separate workflow (managed from the Odoo.sh dashboard) not covered here.\n- OWL JavaScript component migration (legacy widget → OWL v16+) is a complex front-end topic beyond the scope of this skill.\n",{"name":5,"risk":24,"source":25,"description":7},"safe","self","main","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills-claude\u002Fskills\u002Fodoo-upgrade-advisor",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-upgrade-advisor",{"tool":41,"command":42},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill odoo-upgrade-advisor",{"tool":44,"command":45},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill odoo-upgrade-advisor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills-claude\u002Fskills\u002Fodoo-upgrade-advisor\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",[],[]]