odoo-quality
Skill2 starsChanged 3 months agoMITView on GitHub
Functional expertise in Odoo's Quality Management system, covering Control Points, Quality Checks, and Quality Alerts.
In this repository30 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- odoo-attendanceSkill
- odoo-crmSkill
- odoo-dashboardsSkill
- odoo-data-opsSkill
- odoo-devSkill
- odoo-documentsSkill
- odoo-field-serviceSkill
- odoo-financeSkill
- odoo-frontdeskSkill
- odoo-get-startedSkill
- odoo-helpdeskSkill
- odoo-hrSkill
- odoo-introspectorSkill
- odoo-inventorySkill
- odoo-knowledgeSkill
- odoo-mrpSkill
- odoo-plmSkill
- odoo-productsSkill
- odoo-projectsSkill
- odoo-purchasingSkill
- odoo-relationsSkill
- odoo-reportsSkill
- odoo-salesSkill
- odoo-securitySkill
- odoo-spreadsheetsSkill
- odoo-uxSkill
- odoo-websiteSkill
- odoo-worksheetsSkill
- odoo-workspaceSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 18
Inventory: If a stock.picking has pending quality.check records, the picking cannot be validated until all checks are in the pass state.
- Very specific: line 19
Manufacturing: If an mrp.production or mrp.workorder has pending checks, the operation cannot be finished until they are passed.
- Very specific: line 30
Mandate: When creating or managing a quality.alert, the agent must populate the action_corrective and action_preventive fields if a root …
≈ “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.
Files
Skill: Odoo Quality & Compliance
This skill provides the agent with high-level functional expertise in Odoo's Quality Management system, covering Control Points, Quality Checks, and Quality Alerts.
Core Mandates
1. The Quality Hierarchy
- Quality Control Point (
quality.point): The "Rule" or "Trigger". It defines when and where a check should occur (e.g., during Receipt, Manufacturing, or Delivery). - Quality Check (
quality.check): The "Execution". A specific instance of a check triggered by a Control Point. - Quality Alert (
quality.alert): The "Failure/Exception". Created when a check fails or a non-conformance is spotted manually.
2. Workflow Gating
- Mandate: Quality checks are often "blocking" operations.
- Inventory: If a
stock.pickinghas pendingquality.checkrecords, the picking cannot be validated until all checks are in thepassstate. - Manufacturing: If an
mrp.productionormrp.workorderhas pending checks, the operation cannot be finished until they are passed.
3. Check Types & Measurements
Understand the different ways quality is verified:
- Pass/Fail: Simple boolean verification.
- Measure: A numerical value that Odoo validates against
tolerance_minandtolerance_maxdefined on the Point. - Worksheet: A digital form (
worksheet.template) that must be completed and often signed.
4. Alert Workflow (CAPA)
- Corrective Action: Immediate steps taken to fix the specific issue.
- Preventative Action: Long-term steps taken to prevent recurrence.
- Mandate: When creating or managing a
quality.alert, the agent must populate theaction_correctiveandaction_preventivefields if a root cause is identified.
Available Resources
quality-logic.md: Deep-dive into Control Point triggers, Frequency types, and Worksheet integration.quality-fields.json: Dense technical map of fields for Point, Check, and Alert models.
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
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.

