agentleFS
tuanle96tuanle96/mcp-odoo/skills/odoo-data-quality-gate/SKILL.md

odoo-data-quality-gate

Skill421 starsChanged 4 months agoMITView on GitHub

Audit an Odoo database's data quality with evidence before trusting AI answers, importing, or migrating — duplicates, missing required values, orphaned references, format anomalies — and drive remediation through odoo-mcp's gated write workflow. Use when the user asks to "check data quality", "clean up data", "prepare for migration", "find duplicates", or when aggregate answers look suspicious.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    Read summary.checks_with_issues and show evidence: Every finding carries record ids/values — present them in a table (check, issue_count, …

    line 30
  2. Distinctive:

    Re-run the report: after remediation and show the before/after issue counts.

    line 44
  3. Distinctive:

    Read-only by default; every write needs a fresh approval token and the human's explicit confirmation for that batch.

    line 55
  4. Very specific:

    If a check errored (summary.checks_errored), say so — do not present a partial audit as complete.

    line 59

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Odoo data-quality gate

You are running a data-quality audit against a live Odoo database through the odoo-mcp server (tools named data_quality_report, diagnose_access, preview_write, …). Dirty data is the #1 reason ERP AI projects fail — your job is to find issues with evidence and never modify anything without the human approving each batch.

Prerequisites

  • odoo-mcp connected (any Odoo 16+; check with health_check).
  • Writes stay off unless the operator set ODOO_MCP_ENABLE_WRITES=1 — remediation proposals are still valuable without it.

Playbook

  1. Scope with the human. Which models matter? Default set for a general audit: res.partner, product.template, account.move. For migration prep, add every model the custom addons touch (scan_addons_source lists them).
  2. Run the report per model: data_quality_report(model=...). On large databases run it in the background: submit_async_task(operation="data_quality_report", params={"model": ...}) then poll get_async_task.
  3. Read summary.checks_with_issues and show evidence. Every finding carries record ids/values — present them in a table (check, issue_count, sample evidence). Never summarize away the ids; the human needs them.
  4. Verify orphans before judging. orphaned_references cannot tell a dangling reference from a record the current user simply cannot read. For each one, run diagnose_access(model=<target_model>) and report which explanation fits.
  5. Propose remediation as batches, not actions. Group fixes (merge duplicates, fill required fields, archive orphans) into small batches of explicit record ids with the exact new values.
  6. Execute only through the gate, one approved batch at a time: preview_write → show the diff → validate_write → human confirms → execute_approved_write(confirm=true). Never call execute_method for writes; it is blocked by design.
  7. Re-run the report after remediation and show the before/after issue counts.

Output format

A per-model table (check | issue_count | worst evidence | action), a remediation plan ordered by migration risk, and an explicit verdict per model: clean / needs remediation / blocked (explain).

Hard rules

  • Read-only by default; every write needs a fresh approval token and the human's explicit confirmation for that batch.
  • Respect redacted_fields in responses — never ask the user to lift the field ACL to "see more".
  • If a check errored (summary.checks_errored), say so — do not present a partial audit as complete.

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.