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

odoo-products

Skill2 starsChanged 3 months agoMITView on GitHub

MANDATORY for Product Templates (product.template) and Variants (product.product). Expertise in Odoo's catalog and attribute management.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 1 is distinctive, and 6 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.

  • 6

    Very specific

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

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

    Verification: If you need to interact with custom fields or if the user references attributes not in your resource, you MUST call …

    line 13
  2. Very specific:

    Mandate: When executing stock moves, sales lines, or purchase lines, ALWAYS use the ID from product.product.

    line 16
  3. Very specific:

    Mandate: NEVER attempt to modify attribute_line_ids on a product.template that has historical transactions.

    line 19
  4. Distinctive:

    Variant Explosion: Before adding attributes, calculate the total number of variants (Product A x Attribute B x Attribute C).

    line 20
  5. Very specific:

    Mandate: Do not assume accounting properties (Income/Expense accounts) are set on the product level.

    line 23
  6. Very specific:

    Reference First: Search by barcode or default_code (Internal Reference).

    line 37
  7. Very specific:

    Variants: If searching for a specific configuration, search product.product directly using attribute values.

    line 38

≈ “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 Product Management

This skill provides the agent with the expertise required to manage Odoo's product catalog, covering both the general templates and specific product variants.

Core Mandates

1. Snapshot Awareness (Dynamic Discovery)

  • Mandate: The product-fields.json resource is a snapshot of common Odoo fields. It is NOT exhaustive.
  • Verification: If you need to interact with custom fields or if the user references attributes not in your resource, you MUST call inspect_model on product.template or product.product to retrieve the "Live Truth".

2. Template vs. Variant

  • Mandate: When executing stock moves, sales lines, or purchase lines, ALWAYS use the ID from product.product.

2. Attribute Immutability & Safety

  • Mandate: NEVER attempt to modify attribute_line_ids on a product.template that has historical transactions. This is a destructive operation in Odoo.
  • Variant Explosion: Before adding attributes, calculate the total number of variants (Product A x Attribute B x Attribute C). If the resulting count exceeds 50, you MUST seek explicit confirmation from the user due to performance risks.

3. Category-Based Configuration

  • Mandate: Do not assume accounting properties (Income/Expense accounts) are set on the product level. Always check the linked product.category if these fields are null. The category also determines the inventory valuation method (FIFO/AVCO/Standard).

4. Product Types (type field)

  • consu (Goods): Tangible merchandise (storable if is_storable is true).
  • service: Intangible services (never tracked in inventory).
  • combo: A set of other products sold together.

3. Price & Cost

  • list_price: The base Sales Price (on Template).
  • standard_price: The Cost price. Note: This is company-dependent in many configurations.
  • price_extra: Additional cost added to a specific Variant (on Product).

4. Search Workflow

To find a specific product efficiently:

  1. Reference First: Search by barcode or default_code (Internal Reference).
  2. Variants: If searching for a specific configuration, search product.product directly using attribute values.

Available Resources

  • product-logic.md: Deep-dive into variant configuration, attributes, and stock valuation logic.
  • product-fields.json: Dense technical map of fields for both Template and Product 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.