| name | odoo-manufacturing-advisor |
| description | Odoo Manufacturing Advisor workflow skill. Use this skill when the user needs Expert guide for Odoo Manufacturing: Bills of Materials (BoM), Work Centers, routings, MRP planning, and production order workflows and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off. |
| version | 0.0.1 |
| category | frontend |
| tags | ["odoo-manufacturing-advisor","expert","guide","for","odoo","manufacturing","bills","materials"] |
| complexity | intermediate |
| risk | caution |
| tools | ["codex-cli","claude-code","cursor","gemini-cli","opencode"] |
| source | community |
| author | sickn33 |
| date_added | 2026-04-15 |
| date_updated | 2026-04-25 |
Odoo Manufacturing Advisor
Overview
This public intake copy packages plugins/antigravity-awesome-skills-claude/skills/odoo-manufacturing-advisor from https://github.com/sickn33/antigravity-awesome-skills into the native Omni Skills editorial shape without hiding its origin.
Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.
This intake keeps the copied upstream files intact and uses the external_source block in metadata.json plus ORIGIN.md as the provenance anchor for review.
Odoo Manufacturing Advisor
Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: How It Works, Limitations.
When to Use This Skill
Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.
- Creating or structuring Bills of Materials for finished goods.
- Setting up Work Centers with capacity and efficiency settings.
- Running an MRP to automatically generate purchase and production orders from demand.
- Troubleshooting production order discrepancies or component availability issues.
- Use when the request clearly matches the imported source intent: Expert guide for Odoo Manufacturing: Bills of Materials (BoM), Work Centers, routings, MRP planning, and production order workflows.
- Use when the operator should preserve upstream workflow detail instead of rewriting the process from scratch.
Operating Table
| Situation | Start here | Why it matters |
|---|
| First-time use | metadata.json | Confirms repository, branch, commit, and imported path through the external_source block before touching the copied workflow |
| Provenance review | ORIGIN.md | Gives reviewers a plain-language audit trail for the imported source |
| Workflow execution | SKILL.md | Starts with the smallest copied file that materially changes execution |
| Supporting context | SKILL.md | Adds the next most relevant copied source file without loading the entire package |
| Handoff decision | ## Related Skills | Helps the operator switch to a stronger native skill when the task drifts |
Workflow
This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.
- Confirm the user goal, the scope of the imported workflow, and whether this skill is still the right router for the task.
- Read the overview and provenance files before loading any copied upstream support files.
- Load only the references, examples, prompts, or scripts that materially change the outcome for the current request.
- Execute the upstream workflow while keeping provenance and source boundaries explicit in the working notes.
- Validate the result against the upstream expectations and the evidence you can point to in the copied files.
- Escalate or hand off to a related skill when the work moves out of this imported workflow's center of gravity.
- Before merge or closure, record what was used, what changed, and what the reviewer still needs to verify.
Imported Workflow Notes
Imported: Overview
This skill helps you configure and optimize Odoo Manufacturing (MRP). It covers Bills of Materials (BoM), Work Centers, routing operations, production order lifecycle, and Material Requirements Planning (MRP) runs to ensure you never run short of materials.
Imported: How It Works
- Activate: Mention
@odoo-manufacturing-advisor and describe your manufacturing scenario.
- Configure: Receive step-by-step instructions for BoM setup, routing, and MRP configuration.
- Plan: Get guidance on running MRP and interpreting procurement messages.
Examples
Example 1: Ask for the upstream workflow directly
Use @odoo-manufacturing-advisor to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.
Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.
Example 2: Ask for a provenance-grounded review
Review @odoo-manufacturing-advisor against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.
Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.
Example 3: Narrow the copied support files before execution
Use @odoo-manufacturing-advisor for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.
Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.
Example 4: Build a reviewer packet
Review @odoo-manufacturing-advisor using the copied upstream files plus provenance, then summarize any gaps before merge.
Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.
Imported Usage Notes
Imported: Examples
Example 1: Create a Bill of Materials
Menu: Manufacturing → Products → Bills of Materials → New
Product: Finished Widget v2
BoM Type: Manufacture This Product
Quantity: 1 (produce 1 unit per BoM)
Components Tab:
- Raw Plastic Sheet | Qty: 0.5 | Unit: kg
- Steel Bolt M6 | Qty: 4 | Unit: Units
- Rubber Gasket | Qty: 1 | Unit: Units
Operations Tab (requires "Work Orders" enabled in MFG Settings):
- Operation: Injection Molding | Work Center: Press A | Duration: 30 min
- Operation: Assembly | Work Center: Line 1 | Duration: 15 min
BoM Types explained:
- Manufacture This Product — standard production BoM, creates a Manufacturing Order
- Kit — sold as a bundle; components are delivered separately (no MO created)
- Subcontracting — components are sent to a subcontractor who returns the finished product
Example 2: Configure a Work Center
Menu: Manufacturing → Configuration → Work Centers → New
Work Center: CNC Machine 1
Working Hours: Standard 40h/week
Time Efficiency: 85% (machine downtime factored in; 85% = 34 effective hrs/week)
Capacity: 2 (can run 2 production operations simultaneously)
OEE Target: 90% (Overall Equipment Effectiveness KPI target)
Costs per Hour: $75.00 (used for manufacturing cost reporting)
Example 3: Run the MRP Scheduler
The MRP scheduler runs automatically via a daily cron job.
To trigger it manually:
Menu: Inventory → Operations → Replenishment → Run Scheduler
(or Manufacturing → Planning → Replenishment in some versions)
After running, review procurement exceptions:
Menu: Inventory → Operations → Replenishment
Message Types:
"Replenish" — Stock is below minimum; needs a PO or MO
"Reschedule" — An order's scheduled date conflicts with demand
"Cancel" — Demand no longer exists; the order can be cancelled
Best Practices
Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.
- ✅ Do: Enable Work Orders in Manufacturing Settings to use routing and time-tracking per operation.
- ✅ Do: Use BoM with variants (via product attributes) for products that come in multiple configurations (color, size, voltage) — avoids duplicate BoMs.
- ✅ Do: Set Lead Times on components (vendor lead time + security lead time) so MRP schedules purchase orders in advance.
- ✅ Do: Use Scrap Orders when discarding defective components during production — never adjust stock manually.
- ❌ Don't: Manually create purchase orders for MRP-managed items — override MRP suggestions only when justified.
- ❌ Don't: Confuse Kit BoM with Manufacture This Product — a Kit never creates a Manufacturing Order.
- Keep the imported skill grounded in the upstream repository; do not invent steps that the source material cannot support.
Imported Operating Notes
Imported: Best Practices
- ✅ Do: Enable Work Orders in Manufacturing Settings to use routing and time-tracking per operation.
- ✅ Do: Use BoM with variants (via product attributes) for products that come in multiple configurations (color, size, voltage) — avoids duplicate BoMs.
- ✅ Do: Set Lead Times on components (vendor lead time + security lead time) so MRP schedules purchase orders in advance.
- ✅ Do: Use Scrap Orders when discarding defective components during production — never adjust stock manually.
- ❌ Don't: Manually create purchase orders for MRP-managed items — override MRP suggestions only when justified.
- ❌ Don't: Confuse Kit BoM with Manufacture This Product — a Kit never creates a Manufacturing Order.
Troubleshooting
Problem: The operator skipped the imported context and answered too generically
Symptoms: The result ignores the upstream workflow in plugins/antigravity-awesome-skills-claude/skills/odoo-manufacturing-advisor, fails to mention provenance, or does not use any copied source files at all.
Solution: Re-open metadata.json, ORIGIN.md, and the most relevant copied upstream files. Check the external_source block first, then restate the provenance before continuing.
Problem: The imported workflow feels incomplete during review
Symptoms: Reviewers can see the generated SKILL.md, but they cannot quickly tell which references, examples, or scripts matter for the current task.
Solution: Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.
Problem: The task drifted into a different specialization
Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better.
Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.
Related Skills
@00-andruia-consultant - Use when the work is better handled by that native specialization after this imported skill establishes context.@00-andruia-consultant-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.@10-andruia-skill-smith - Use when the work is better handled by that native specialization after this imported skill establishes context.@10-andruia-skill-smith-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
Additional Resources
Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.
| Resource family | What it gives the reviewer | Example path |
|---|
references | copied reference notes, guides, or background material from upstream | references/n/a |
examples | worked examples or reusable prompts copied from upstream | examples/n/a |
scripts | upstream helper scripts that change execution or validation | scripts/n/a |
agents | routing or delegation notes that are genuinely part of the imported package | agents/n/a |
assets | supporting assets or schemas copied from the source package | assets/n/a |
Imported Reference Notes
Imported: Limitations
- This skill targets Odoo Manufacturing (mrp) module. Maintenance, PLM (Product Lifecycle Management), and Quality modules are separate Enterprise modules not covered here.
- Subcontracting workflows (sending components to a third-party manufacturer) have additional receipt and valuation steps not fully detailed here.
- Lot/serial number traceability in production (tracking which lot was consumed per MO) adds complexity; test with small batches before full rollout.
- MRP calculations assume demand comes from Sale Orders and Reordering Rules — forecasts from external systems require custom integration.
