agentleFS
dimastrianndimastriann/odoo-erp-mcp/.agents/skills/odoo-compat/SKILL.md

odoo-compat

Skill3 starsChanged 9 days agoMITView on GitHub

Use when changing Odoo version handling, RPC transport, authentication, retries, timeouts, error classification, or response parsing. Ensures Odoo v12-v19+ compatibility without live-server tests.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    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:

    Keep the configured and current transport distinction and the atomic transport switch in src/odoo/client.rs.

    line 16
  2. Distinctive:

    Treat unknown versions conservatively.

    line 24
  3. Distinctive:

    Keep version-probing failures non-fatal for auto mode.

    line 25
  4. Distinctive:

    Update the README support matrix only when behavior actually changes.

    line 26
  5. Distinctive:

    Never retry mutations or authentication failures.

    line 34
  6. Distinctive:

    Keep method names and argument shapes version-compatible.

    line 41
  7. Distinctive:

    Do not add Odoo-version-specific behavior inside tool handlers.

    line 42
  8. Very specific:

    Use src/test_support.rs mocked servers.

    line 48
  9. Distinctive:

    Run the full quality gate from AGENTS.md.

    line 60
  10. Distinctive:

    Check that the change does not weaken TLS verification, credential handling, or error redaction.

    line 61

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

AGENTS.md is the canonical rule set. Keep one client boundary in src/odoo/; tools and lifecycle code must not depend on transport details.

1. Transport selection

  • RpcTransport supports auto, jsonrpc, and json2.
  • auto probes common.version; use JSON-2 for Odoo 19+ and fall back to JSON-RPC when JSON-2 rejects the credential.
  • Keep the configured and current transport distinction and the atomic transport switch in src/odoo/client.rs.
  • JSON-2 uses bearer API keys and named arguments; JSON-RPC uses the classic envelope. Preserve request-body and response-normalization behavior.

2. Version handling

  • Parse server_version_info first, then server_version as a fallback.
  • Treat unknown versions conservatively; do not assume JSON-2 support.
  • Keep version-probing failures non-fatal for auto mode.
  • Update the README support matrix only when behavior actually changes.

3. Errors and retries

  • Classify transport, timeout, protocol, authentication, validation, and access errors through AppError; never string-match raw Odoo text.
  • Retry only read-only operations, only transient errors, with bounded exponential backoff and jitter.
  • Never retry mutations or authentication failures.
  • Preserve response-size limits and timeouts.
  • Record retry metrics and events without leaking payloads or credentials.

4. Odoo semantics

  • Respect JSON-RPC versus JSON-2 differences for create and read_group results.
  • Keep method names and argument shapes version-compatible.
  • Do not add Odoo-version-specific behavior inside tool handlers; keep it in the client or a dedicated compatibility module.
  • Preserve context validation and per-instance query limits.

5. Tests

Use src/test_support.rs mocked servers; no live Odoo instance.

  • transport auto-selection for Odoo 18 and 19+;
  • JSON-2 bearer headers and named arguments;
  • JSON-2 result normalization;
  • fallback from JSON-2 to JSON-RPC on rejected credentials;
  • timeout, protocol, authentication, and malformed-envelope categories;
  • retry success, retry exhaustion, and no-retry for mutations and auth;
  • response-size and timeout limits.

6. Review

  • Run the full quality gate from AGENTS.md.
  • Check that the change does not weaken TLS verification, credential handling, or error redaction.

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.