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.
In this repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- atomic-commitSkill
- mcp-tool-extensionSkill
- mutation-lifecycleSkill
- releaseSkill
- security-reviewSkill
- web-uiSkill
- atomic-commitSkill
- mcp-tool-extensionSkill
- mutation-lifecycleSkill
- odoo-compatSkill
- releaseSkill
- security-reviewSkill
- web-uiSkill
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
- Very specific: line 16
Keep the configured and current transport distinction and the atomic transport switch in src/odoo/client.rs.
- Distinctive: line 24
Treat unknown versions conservatively.
- Distinctive: line 25
Keep version-probing failures non-fatal for auto mode.
- Distinctive: line 26
Update the README support matrix only when behavior actually changes.
- Distinctive: line 34
Never retry mutations or authentication failures.
- Distinctive: line 41
Keep method names and argument shapes version-compatible.
- Distinctive: line 42
Do not add Odoo-version-specific behavior inside tool handlers.
- Very specific: line 48
Use src/test_support.rs mocked servers.
- Distinctive: line 60
Run the full quality gate from AGENTS.md.
- Distinctive: line 61
Check that the change does not weaken TLS verification, credential handling, or error redaction.
≈ “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.
Files
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
RpcTransportsupportsauto,jsonrpc, andjson2.autoprobescommon.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_infofirst, thenserver_versionas 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
contextvalidation 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.
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.

