[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CMHFGSDBPYRT4TFREPBFPX":3,"skill-same:01M7CMHFGSDBPYRT4TFREPBFPX":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},"01M7CMHFGSDBPYRT4TFREPBFPX","odoo-inventory-optimizer",null,"Expert guide for Odoo Inventory: stock valuation (FIFO\u002FAVCO), reordering rules, putaway strategies, routes, and multi-warehouse configuration.","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-inventory-optimizer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: odoo-inventory-optimizer\ndescription: \"Expert guide for Odoo Inventory: stock valuation (FIFO\u002FAVCO), reordering rules, putaway strategies, routes, and multi-warehouse configuration.\"\nrisk: safe\nsource: \"self\"\n---\n\n# Odoo Inventory Optimizer\n\n## Overview\n\nThis skill helps you configure and optimize Odoo Inventory for accuracy, efficiency, and traceability. It covers stock valuation methods, reordering rules, putaway strategies, warehouse routes, and multi-step flows (receive → quality → store).\n\n## When to Use This Skill\n\n- Choosing and configuring FIFO vs AVCO stock valuation.\n- Setting up minimum stock reordering rules to avoid stockouts.\n- Designing a multi-step warehouse flow (2-step receipt, 3-step delivery).\n- Configuring putaway rules to direct products to specific storage locations.\n- Troubleshooting negative stock, incorrect valuation, or missing moves.\n\n## How It Works\n\n1. **Activate**: Mention `@odoo-inventory-optimizer` and describe your warehouse scenario.\n2. **Configure**: Receive step-by-step configuration instructions with exact Odoo menu paths.\n3. **Optimize**: Get recommendations for reordering rules and stock accuracy improvements.\n\n## Examples\n\n### Example 1: Enable FIFO Stock Valuation\n\n```text\nMenu: Inventory → Configuration → Settings\n\nEnable: Storage Locations\nEnable: Multi-Step Routes\nCosting Method: (set per Product Category, not globally)\n\nMenu: Inventory → Configuration → Product Categories → Edit\n\n  Category: All \u002F Physical Goods\n  Costing Method: First In First Out (FIFO)\n  Inventory Valuation: Automated\n  Account Stock Valuation: [Balance Sheet inventory account]\n  Account Stock Input:   [Stock Received Not Billed]\n  Account Stock Output:  [Stock Delivered Not Invoiced]\n```\n\n### Example 2: Set Up a Min\u002FMax Reordering Rule\n\n```text\nMenu: Inventory → Operations → Replenishment → New\n\nProduct: Office Paper A4\nLocation: WH\u002FStock\nMin Qty: 100   (trigger reorder when stock falls below this)\nMax Qty: 500   (purchase up to this quantity)\nMultiple Qty: 50  (always order in multiples of 50)\nRoute: Buy    (triggers a Purchase Order automatically)\n       or Manufacture (triggers a Manufacturing Order)\n```\n\n### Example 3: Configure Putaway Rules\n\n```text\nMenu: Inventory → Configuration → Putaway Rules → New\n\nPurpose: Direct products from WH\u002FInput to specific bin locations\n\nRules:\n  Product Category: Refrigerated Goods\n    → Location: WH\u002FStock\u002FCold Storage\n\n  Product: Laptop Model X\n    → Location: WH\u002FStock\u002FElectronics\u002FShelf A\n\n  (leave Product blank to apply the rule to an entire category)\n\nResult: When a receipt is validated, Odoo automatically suggests\nthe correct destination location per product or category.\n```\n\n### Example 4: Configure 3-Step Warehouse Delivery\n\n```text\nMenu: Inventory → Configuration → Warehouses → [Your Warehouse]\n\nOutgoing Shipments: Pick + Pack + Ship (3 steps)\n\nOperations created automatically:\n  PICK  — Move goods from storage shelf to packing area\n  PACK  — Package items and print shipping label\n  OUT   — Hand off to carrier \u002F mark as shipped\n```\n\n## Best Practices\n\n- ✅ **Do:** Use **Lots\u002FSerial Numbers** for high-value or regulated items (medical devices, electronics).\n- ✅ **Do:** Run a **physical inventory adjustment** at least quarterly (Inventory → Operations → Physical Inventory) to correct drift.\n- ✅ **Do:** Set reordering rules on fast-moving items so purchase orders are generated automatically.\n- ✅ **Do:** Enable **Putaway Rules** on warehouses with multiple storage zones — it eliminates manual location selection errors.\n- ❌ **Don't:** Switch stock valuation method (FIFO ↔ AVCO) after recording transactions — it produces incorrect historical cost data.\n- ❌ **Don't:** Use \"Update Quantity\" to fix stock errors — always use Inventory Adjustments to maintain a proper audit trail.\n- ❌ **Don't:** Mix product categories with different costing methods in the same storage location without understanding the valuation impact.\n\n## Limitations\n\n- **Serial number tracking** at the individual unit level (SN per line) adds significant UI overhead; test performance with large volumes before enabling.\n- Does not cover **landed costs** (import duties, freight allocation to product cost) — that requires the `stock_landed_costs` module.\n- **Cross-warehouse stock transfers** have routing complexities (transit locations, intercompany invoicing) not fully covered here.\n- Automated inventory valuation requires the **Accounting** module; Community Edition installations without it cannot post stock journal entries.\n","# Odoo Inventory Optimizer\n\n## Overview\n\nThis skill helps you configure and optimize Odoo Inventory for accuracy, efficiency, and traceability. It covers stock valuation methods, reordering rules, putaway strategies, warehouse routes, and multi-step flows (receive → quality → store).\n\n## When to Use This Skill\n\n- Choosing and configuring FIFO vs AVCO stock valuation.\n- Setting up minimum stock reordering rules to avoid stockouts.\n- Designing a multi-step warehouse flow (2-step receipt, 3-step delivery).\n- Configuring putaway rules to direct products to specific storage locations.\n- Troubleshooting negative stock, incorrect valuation, or missing moves.\n\n## How It Works\n\n1. **Activate**: Mention `@odoo-inventory-optimizer` and describe your warehouse scenario.\n2. **Configure**: Receive step-by-step configuration instructions with exact Odoo menu paths.\n3. **Optimize**: Get recommendations for reordering rules and stock accuracy improvements.\n\n## Examples\n\n### Example 1: Enable FIFO Stock Valuation\n\n```text\nMenu: Inventory → Configuration → Settings\n\nEnable: Storage Locations\nEnable: Multi-Step Routes\nCosting Method: (set per Product Category, not globally)\n\nMenu: Inventory → Configuration → Product Categories → Edit\n\n  Category: All \u002F Physical Goods\n  Costing Method: First In First Out (FIFO)\n  Inventory Valuation: Automated\n  Account Stock Valuation: [Balance Sheet inventory account]\n  Account Stock Input:   [Stock Received Not Billed]\n  Account Stock Output:  [Stock Delivered Not Invoiced]\n```\n\n### Example 2: Set Up a Min\u002FMax Reordering Rule\n\n```text\nMenu: Inventory → Operations → Replenishment → New\n\nProduct: Office Paper A4\nLocation: WH\u002FStock\nMin Qty: 100   (trigger reorder when stock falls below this)\nMax Qty: 500   (purchase up to this quantity)\nMultiple Qty: 50  (always order in multiples of 50)\nRoute: Buy    (triggers a Purchase Order automatically)\n       or Manufacture (triggers a Manufacturing Order)\n```\n\n### Example 3: Configure Putaway Rules\n\n```text\nMenu: Inventory → Configuration → Putaway Rules → New\n\nPurpose: Direct products from WH\u002FInput to specific bin locations\n\nRules:\n  Product Category: Refrigerated Goods\n    → Location: WH\u002FStock\u002FCold Storage\n\n  Product: Laptop Model X\n    → Location: WH\u002FStock\u002FElectronics\u002FShelf A\n\n  (leave Product blank to apply the rule to an entire category)\n\nResult: When a receipt is validated, Odoo automatically suggests\nthe correct destination location per product or category.\n```\n\n### Example 4: Configure 3-Step Warehouse Delivery\n\n```text\nMenu: Inventory → Configuration → Warehouses → [Your Warehouse]\n\nOutgoing Shipments: Pick + Pack + Ship (3 steps)\n\nOperations created automatically:\n  PICK  — Move goods from storage shelf to packing area\n  PACK  — Package items and print shipping label\n  OUT   — Hand off to carrier \u002F mark as shipped\n```\n\n## Best Practices\n\n- ✅ **Do:** Use **Lots\u002FSerial Numbers** for high-value or regulated items (medical devices, electronics).\n- ✅ **Do:** Run a **physical inventory adjustment** at least quarterly (Inventory → Operations → Physical Inventory) to correct drift.\n- ✅ **Do:** Set reordering rules on fast-moving items so purchase orders are generated automatically.\n- ✅ **Do:** Enable **Putaway Rules** on warehouses with multiple storage zones — it eliminates manual location selection errors.\n- ❌ **Don't:** Switch stock valuation method (FIFO ↔ AVCO) after recording transactions — it produces incorrect historical cost data.\n- ❌ **Don't:** Use \"Update Quantity\" to fix stock errors — always use Inventory Adjustments to maintain a proper audit trail.\n- ❌ **Don't:** Mix product categories with different costing methods in the same storage location without understanding the valuation impact.\n\n## Limitations\n\n- **Serial number tracking** at the individual unit level (SN per line) adds significant UI overhead; test performance with large volumes before enabling.\n- Does not cover **landed costs** (import duties, freight allocation to product cost) — that requires the `stock_landed_costs` module.\n- **Cross-warehouse stock transfers** have routing complexities (transit locations, intercompany invoicing) not fully covered here.\n- Automated inventory valuation requires the **Accounting** module; Community Edition installations without it cannot post stock journal entries.\n",{"name":5,"risk":24,"source":25,"description":7},"safe","self","main","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fskills\u002Fodoo-inventory-optimizer",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-inventory-optimizer",{"tool":41,"command":42},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill odoo-inventory-optimizer",{"tool":44,"command":45},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill odoo-inventory-optimizer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fskills\u002Fodoo-inventory-optimizer\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",[],[]]