agentleFS
actinon-comactinon-com/brass-monkey/skills/odoo-sales/SKILL.md

odoo-sales

Skill2 starsChanged 3 months agoMITView on GitHub

MANDATORY for Sales Orders (sale.order), Quotations, and Order Fulfillment. Functional expertise in Odoo's Sales engine and lifecycle states.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Product Identification: ALWAYS use the product.product ID on lines.

    line 16
  2. Distinctive:

    Delivered Quantities: Only invoice what has been physically shipped or performed.

    line 23
  3. Very specific:

    Check: Use the invoice_status field to determine if a record is to invoice.

    line 24

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Skill: Odoo Sales & Order Fulfillment

This skill provides the agent with high-level functional expertise in Odoo's Sales engine, covering the entire lifecycle from Quotation to Order Fulfillment (Shipping, Manufacturing, Services).

Core Mandates

1. The Sales Lifecycle

  • States: draft (Quotation) -> sent (Quotation Sent) -> sale (Confirmed Order) -> cancel.
  • Confirmation Trigger: Confirming an SO (action_confirm) is a critical event that automatically triggers downstream operations (e.g., Delivery Orders, Manufacturing Orders, or Project Tasks).

2. Line Management & Pricing

  • Product Identification: ALWAYS use the product.product ID on lines.
  • Pricelists: Pricing is dynamically determined by the pricelist_id. Do not assume the price on the line is static; it may change based on quantities or customer tiers.
  • Taxes: Taxes are computed automatically based on the product and the fiscal_position_id of the partner.

3. Invoicing Policies

Understand when an order is ready for billing:

  • Ordered Quantities: Invoice the customer as soon as the SO is confirmed.
  • Delivered Quantities: Only invoice what has been physically shipped or performed.
  • Check: Use the invoice_status field to determine if a record is to invoice.

4. Advanced Fulfillment Strategies

Support complex business scenarios:

  • Services: Manage service_tracking to create Projects or Tasks automatically upon confirmation.
  • Make to Order (MTO) / Build to Order (BTO): Understand how routes trigger immediate supply chain actions.
  • Engineer to Order (ETO): Link Sales Orders to bespoke design Tasks before final quoting.
  • Dropshipping: Automatically generate a Purchase Order targeting the customer's address.

Available Resources

  • sales-logic.md: Deep-dive into fulfillment scenarios (MTO, ETO, Services), Pricelists, and Invoicing rules.
  • sales-fields.json: Dense technical map of fields for Order, Line, Pricelist, and Payment Term models.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.