BF drivethru-production-scheduler
Schedule MRP production batches in Odoo (BaconCo) — the fluid shop-floor scheduler. Periodically read open `mrp.production.batch` records, rank them into a run order by the shop rule (manual pins first, then art readiness, then imminent event dates, then earliest governing deadline), write that order back to the floor, and refine it into machine + time slots where the picture is solid. Defers batches whose decals aren't printed or whose artwork isn't digitized below work that can actually run, and expedites them to the top once they're about to be late. Reads purchase orders + vendor tracking to know when goods will land, and uses receipt-readiness as guidance (jobs generally shouldn't start before their components are in) that it refines from human feedback. Handles rush orders dropped in mid-day by re-ranking. Talks to Odoo through the `drivethru_mcp` MCP server. Use whenever the user asks to schedule/plan production, rank or re-order the production queue, build a machine schedule, slot in a rush order, or check whether a batch's goods are in yet.
Schedule MRP production batches in Odoo (BaconCo) — the fluid shop-floor scheduler.
As a process F 48/100 · Will not run — References files that are not bundled: references/scheduling_algorithm.md, references/receipt_readiness.md, scripts/odoo_mcp.py
How to improve
- Shorten the description to 1024 characters.
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 0. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
description-longdescription is 1065 chars, limit 1024 - warning
missing-refreference to a missing file: references/scheduling_algorithm.md - warning
missing-refreference to a missing file: references/receipt_readiness.md - warning
missing-refreference to a missing file: scripts/odoo_mcp.py - note
frontmatter-keyunknown frontmatter key "emoji" - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 48/100
- 0Tools and files. 3 referenced file(s) missing: references/scheduling_algorithm.md, references/receipt_readiness.md, scripts/odoo_mcp.py
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 4 mutating operations with no state check
- 70When it triggers. States when to use, but not when not to
- 85Steps. 38 steps, 1 vague phrases
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3074 tokens
- 100Progress reporting. Reports progress
- low 11 top-level sections: this looks like several domains in one skill
- high The skill tells the model to perform an irreversible action with no human approval
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 1065: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 12 headings
- +3Step-by-step instructions: 38 items
- +4Has examples (2 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 42.