[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CMH8T8PRMRYFNTYBR3YENJ":3,"skill-same:01M7CMH8T8PRMRYFNTYBR3YENJ":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},"01M7CMH8T8PRMRYFNTYBR3YENJ","odoo-edi-connector",null,"Guide for implementing EDI (Electronic Data Interchange) with Odoo: X12, EDIFACT document mapping, partner onboarding, and automated order processing.","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-edi-connector\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: odoo-edi-connector\ndescription: \"Guide for implementing EDI (Electronic Data Interchange) with Odoo: X12, EDIFACT document mapping, partner onboarding, and automated order processing.\"\nrisk: unknown\nsource: community\n---\n\n# Odoo EDI Connector\n\n## Overview\n\nElectronic Data Interchange (EDI) is the standard for automated B2B document exchange — purchase orders, invoices, ASNs (Advance Shipping Notices). This skill guides you through mapping EDI transactions (ANSI X12 or EDIFACT) to Odoo business objects, setting up trading partner configurations, and automating inbound\u002Foutbound document flows.\n\n## When to Use This Skill\n\n- A retail partner requires EDI 850 (Purchase Orders) to do business with you.\n- You need to send EDI 856 (ASN) when goods are shipped.\n- Automating EDI 810 (Invoice) generation from Odoo confirmed deliveries.\n- Mapping EDI fields to Odoo fields for a new trading partner.\n\n## How It Works\n\n1. **Activate**: Mention `@odoo-edi-connector` and specify the EDI transaction set and trading partner.\n2. **Map**: Receive a complete field mapping table between EDI segments and Odoo fields.\n3. **Automate**: Get Python code to parse incoming EDI files and create Odoo records.\n\n## EDI ↔ Odoo Object Mapping\n\n| EDI Transaction | Odoo Object |\n|---|---|\n| 850 Purchase Order | `sale.order` (inbound customer PO) |\n| 855 PO Acknowledgment | Confirmation email \u002F SO confirmation |\n| 856 ASN (Advance Ship Notice) | `stock.picking` (delivery order) |\n| 810 Invoice | `account.move` (customer invoice) |\n| 846 Inventory Inquiry | `product.product` stock levels |\n| 997 Functional Acknowledgment | Automated receipt confirmation |\n\n## Examples\n\n### Example 1: Parse EDI 850 and Create Odoo Sale Order (Python)\n\n```python\nfrom pyx12 import x12file  # pip install pyx12\nfrom datetime import datetime\n\nimport xmlrpc.client\nimport os\n\nodoo_url = os.getenv(\"ODOO_URL\")\ndb = os.getenv(\"ODOO_DB\")\npwd = os.getenv(\"ODOO_API_KEY\") \nuid = int(os.getenv(\"ODOO_UID\", \"2\"))\n\nmodels = xmlrpc.client.ServerProxy(f\"{odoo_url}\u002Fxmlrpc\u002F2\u002Fobject\")\n\ndef process_850(edi_file_path):\n    \"\"\"Parse X12 850 Purchase Order and create Odoo Sale Order\"\"\"\n    with x12file.X12File(edi_file_path) as f:\n        for transaction in f.get_transaction_sets():\n            # Extract header info (BEG segment)                     \n            po_number = transaction['BEG'][3]    # Purchase Order Number                                                    \n            po_date   = transaction['BEG'][5]    # Purchase Order Date \n\n            # IDEMPOTENCY CHECK: Verify PO doesn't already exist in Odoo\n            existing = models.execute_kw(db, uid, pwd, 'sale.order', 'search', [\n                [['client_order_ref', '=', po_number]]\n            ])\n            if existing:\n                print(f\"Skipping: PO {po_number} already exists.\")\n                continue \n\n            # Extract partner (N1 segment — Buyer)\n\n\n                        # Extract partner (N1 segment — Buyer)                  \n            partner_name = transaction.get_segment('N1')[2] if transaction.get_segment('N1') else \"Unknown\"                                                                             \n            \n            # Find partner in Odoo                                  \n            partner = models.execute_kw(db, uid, pwd, 'res.partner', 'search',                                                  \n                                [[['name', 'ilike', partner_name]]])                \n            \n            if not partner:\n                print(f\"Error: Partner '{partner_name}' not found. Skipping transaction.\")\n                continue\n                \n            partner_id = partner[0]\n\n            # Extract line items (PO1 segments)\n            order_lines = []\n            for po1 in transaction.get_segments('PO1'):\n                sku     = po1[7]    # Product ID\n                qty     = float(po1[2])\n                price   = float(po1[4])\n\n                product = models.execute_kw(db, uid, pwd, 'product.product', 'search',\n                    [[['default_code', '=', sku]]])\n                if product:\n                    order_lines.append((0, 0, {\n                        'product_id': product[0],\n                        'product_uom_qty': qty,\n                        'price_unit': price,\n                    }))\n\n            # Create Sale Order\n            if partner_id and order_lines:\n                models.execute_kw(db, uid, pwd, 'sale.order', 'create', [{\n                    'partner_id': partner_id,\n                    'client_order_ref': po_number,\n                    'order_line': order_lines,\n                }])\n```\n\n### Example 2: Send EDI 997 Acknowledgment\n\n```python\ndef generate_997(isa_control, gs_control, transaction_control):\n    \"\"\"Generate a functional acknowledgment for received EDI\"\"\"\n    today = datetime.now().strftime('%y%m%d')\n    return f\"\"\"ISA*00*          *00*          *ZZ*YOURISAID      *ZZ*PARTNERISAID   *{today}*1200*^*00501*{isa_control}*0*P*>~\nGS*FA*YOURGID*PARTNERGID*{today}*1200*{gs_control}*X*005010X231A1~\nST*997*0001~\nAK1*PO*{gs_control}~\nAK9*A*1*1*1~\nSE*4*0001~\nGE*1*{gs_control}~\nIEA*1*{isa_control}~\"\"\"\n```\n\n## Best Practices\n\n- ✅ **Do:** Store every raw EDI transaction in an audit log table before processing.\n- ✅ **Do:** Always send a **997 Functional Acknowledgment** within 24 hours of receiving a transaction.\n- ✅ **Do:** Negotiate a test cycle with trading partners before going live — use test ISA qualifier `T`.\n- ❌ **Don't:** Process EDI files synchronously in web requests — queue them for async processing.\n- ❌ **Don't:** Hardcode trading partner qualifiers — store them in a configuration table per partner.\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n","# Odoo EDI Connector\n\n## Overview\n\nElectronic Data Interchange (EDI) is the standard for automated B2B document exchange — purchase orders, invoices, ASNs (Advance Shipping Notices). This skill guides you through mapping EDI transactions (ANSI X12 or EDIFACT) to Odoo business objects, setting up trading partner configurations, and automating inbound\u002Foutbound document flows.\n\n## When to Use This Skill\n\n- A retail partner requires EDI 850 (Purchase Orders) to do business with you.\n- You need to send EDI 856 (ASN) when goods are shipped.\n- Automating EDI 810 (Invoice) generation from Odoo confirmed deliveries.\n- Mapping EDI fields to Odoo fields for a new trading partner.\n\n## How It Works\n\n1. **Activate**: Mention `@odoo-edi-connector` and specify the EDI transaction set and trading partner.\n2. **Map**: Receive a complete field mapping table between EDI segments and Odoo fields.\n3. **Automate**: Get Python code to parse incoming EDI files and create Odoo records.\n\n## EDI ↔ Odoo Object Mapping\n\n| EDI Transaction | Odoo Object |\n|---|---|\n| 850 Purchase Order | `sale.order` (inbound customer PO) |\n| 855 PO Acknowledgment | Confirmation email \u002F SO confirmation |\n| 856 ASN (Advance Ship Notice) | `stock.picking` (delivery order) |\n| 810 Invoice | `account.move` (customer invoice) |\n| 846 Inventory Inquiry | `product.product` stock levels |\n| 997 Functional Acknowledgment | Automated receipt confirmation |\n\n## Examples\n\n### Example 1: Parse EDI 850 and Create Odoo Sale Order (Python)\n\n```python\nfrom pyx12 import x12file  # pip install pyx12\nfrom datetime import datetime\n\nimport xmlrpc.client\nimport os\n\nodoo_url = os.getenv(\"ODOO_URL\")\ndb = os.getenv(\"ODOO_DB\")\npwd = os.getenv(\"ODOO_API_KEY\") \nuid = int(os.getenv(\"ODOO_UID\", \"2\"))\n\nmodels = xmlrpc.client.ServerProxy(f\"{odoo_url}\u002Fxmlrpc\u002F2\u002Fobject\")\n\ndef process_850(edi_file_path):\n    \"\"\"Parse X12 850 Purchase Order and create Odoo Sale Order\"\"\"\n    with x12file.X12File(edi_file_path) as f:\n        for transaction in f.get_transaction_sets():\n            # Extract header info (BEG segment)                     \n            po_number = transaction['BEG'][3]    # Purchase Order Number                                                    \n            po_date   = transaction['BEG'][5]    # Purchase Order Date \n\n            # IDEMPOTENCY CHECK: Verify PO doesn't already exist in Odoo\n            existing = models.execute_kw(db, uid, pwd, 'sale.order', 'search', [\n                [['client_order_ref', '=', po_number]]\n            ])\n            if existing:\n                print(f\"Skipping: PO {po_number} already exists.\")\n                continue \n\n            # Extract partner (N1 segment — Buyer)\n\n\n                        # Extract partner (N1 segment — Buyer)                  \n            partner_name = transaction.get_segment('N1')[2] if transaction.get_segment('N1') else \"Unknown\"                                                                             \n            \n            # Find partner in Odoo                                  \n            partner = models.execute_kw(db, uid, pwd, 'res.partner', 'search',                                                  \n                                [[['name', 'ilike', partner_name]]])                \n            \n            if not partner:\n                print(f\"Error: Partner '{partner_name}' not found. Skipping transaction.\")\n                continue\n                \n            partner_id = partner[0]\n\n            # Extract line items (PO1 segments)\n            order_lines = []\n            for po1 in transaction.get_segments('PO1'):\n                sku     = po1[7]    # Product ID\n                qty     = float(po1[2])\n                price   = float(po1[4])\n\n                product = models.execute_kw(db, uid, pwd, 'product.product', 'search',\n                    [[['default_code', '=', sku]]])\n                if product:\n                    order_lines.append((0, 0, {\n                        'product_id': product[0],\n                        'product_uom_qty': qty,\n                        'price_unit': price,\n                    }))\n\n            # Create Sale Order\n            if partner_id and order_lines:\n                models.execute_kw(db, uid, pwd, 'sale.order', 'create', [{\n                    'partner_id': partner_id,\n                    'client_order_ref': po_number,\n                    'order_line': order_lines,\n                }])\n```\n\n### Example 2: Send EDI 997 Acknowledgment\n\n```python\ndef generate_997(isa_control, gs_control, transaction_control):\n    \"\"\"Generate a functional acknowledgment for received EDI\"\"\"\n    today = datetime.now().strftime('%y%m%d')\n    return f\"\"\"ISA*00*          *00*          *ZZ*YOURISAID      *ZZ*PARTNERISAID   *{today}*1200*^*00501*{isa_control}*0*P*>~\nGS*FA*YOURGID*PARTNERGID*{today}*1200*{gs_control}*X*005010X231A1~\nST*997*0001~\nAK1*PO*{gs_control}~\nAK9*A*1*1*1~\nSE*4*0001~\nGE*1*{gs_control}~\nIEA*1*{isa_control}~\"\"\"\n```\n\n## Best Practices\n\n- ✅ **Do:** Store every raw EDI transaction in an audit log table before processing.\n- ✅ **Do:** Always send a **997 Functional Acknowledgment** within 24 hours of receiving a transaction.\n- ✅ **Do:** Negotiate a test cycle with trading partners before going live — use test ISA qualifier `T`.\n- ❌ **Don't:** Process EDI files synchronously in web requests — queue them for async processing.\n- ❌ **Don't:** Hardcode trading partner qualifiers — store them in a configuration table per partner.\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n",{"name":5,"risk":24,"source":25,"description":7},"unknown","community","main","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fskills\u002Fodoo-edi-connector",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-edi-connector",{"tool":41,"command":42},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill odoo-edi-connector",{"tool":44,"command":45},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill odoo-edi-connector","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fskills\u002Fodoo-edi-connector\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",[],[]]