odoo-backend
- Repo stars 0
- Author updated Live
- Author repo skills-registry
- Domain
- Data
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @tomevault-io · no license declared
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- Python
- Permissions
-
- Read-only
- Write / modify
- Shell exec
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: odoo-backend
description: Use when working on Odoo 19 server-side code or backend tests: Python models, ORM recordsets, fi…
category: data
runtime: Python
---
# odoo-backend output preview
## PART A: Task fit
- Use case: Use when working on Odoo 19 server-side code or backend tests: Python models, ORM recordsets, fields/decorators, domains, SQL/cache, `__manifest__.py`, XML/CSV data, ACLs/rules, `sudo`, controllers, `@route`, `ir.cron`, JSON-2/XML-RPC, QWeb reports, `TransactionCase`, `HttpCase`, `Form`, tours, `start_tour`, or `--test-tags`. Not for web-client JS, Owl internals, Hoot, frontend assets, views, or widgets..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Quick Route / Backend Defaults / Cross-Skill Guidance” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Use when working on Odoo 19 server-side code or backend tests: Python models, ORM recordsets, fields/decorators, domains, SQL/cache, `__manifest__.py`, XML/CSV data, ACLs/rules, `sudo`, controllers, `@route`, `ir.cron`, JSON-2/XML-RPC, QWeb reports, `TransactionCase`, `HttpCase`, `Form`, tours, `start_tour`, or `--test-tags`. Not for web-client JS, Owl internals, Hoot, frontend assets, views, or widgets.”.
- **02** When the source has headings, the agent prioritizes “Quick Route / Backend Defaults / Cross-Skill Guidance” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source mentions slash commands such as `/json`; use them first when your agent supports command triggers.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files, run shell commands.
Validate with a small run
Start with a small task and check whether the result follows “Quick Route / Backend Defaults / Cross-Skill Guidance”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: odoo-backend
description: Use when working on Odoo 19 server-side code or backend tests: Python models, ORM recordsets, fi…
category: data
source: tomevault-io/skills-registry
---
# odoo-backend
## When to use
- Use when working on Odoo 19 server-side code or backend tests: Python models, ORM recordsets, fields/decorators, domai…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Quick Route / Backend Defaults / Cross-Skill Guidance” and keep inference separate from source facts.
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "odoo-backend" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Quick Route / Backend Defaults / Cross-Skill Guidance
rules -> SKILL.md triggers / order / output contract
runtime -> Python | read files, write/modify files, run shell commands | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}The skill is based on Odoo 19.0 backend and external API documentation, generated at 2026-04-22.
Odoo 19 Backend
Use this for Odoo-specific server behavior agents often get wrong. It skips generic Python, ORM, and XML material. Load only the narrowest reference that matches the task.
Quick Route
| If the task is about... | Read |
|---|---|
__manifest__.py, XML/CSV loading, record/function tags, noupdate |
core-module-structure-and-data |
recordsets, _inherit, _inherits, reserved fields, constraint/index attrs |
core-orm-models-recordsets |
computed/related fields, @api.depends, @api.onchange, @api.constrains, @api.model_create_multi, @api.private |
core-fields-and-decorators |
domains, search_fetch, _read_group, raw SQL, SQL(...), flushing, cache invalidation, modified(...) |
core-domains-sql-and-cache |
ACL CSVs, record rules, sudo, field groups=, RPC exposure, SQL injection, safe_eval, escaping HTML |
core-security-acl-and-rules |
action dicts, ir.actions.server, ir.cron, _commit_progress |
features-actions-and-cron |
Python controllers, @route, request env, controller inheritance |
features-controllers-and-http |
external integrations, bearer-key JSON-2, /json/2, legacy XML-RPC / JSON-RPC execute_kw |
features-external-api-and-rpc |
QWeb PDF/HTML reports, paper formats, custom _get_report_values, report assets/fonts |
features-qweb-reports |
mail.thread, aliases, activities, common backend mixins |
features-common-mixins |
TransactionCase, HttpCase, Form, --test-tags, tours, query-count assertions |
testing-backend-and-tours |
| profiling, batching, prefetch, query budgets, indexes | performance-profiling-and-batching |
| final review pass, Odoo 19 deltas, common regressions | best-practices-odoo-19-backend |
Backend Defaults
- Model methods may receive empty or multi-record
self; enforce singleton semantics explicitly. - Public model methods are RPC-reachable. Keep security in Python, ACLs, and rules, not only in views.
- Prefer ORM. If SQL is necessary, flush before reads/writes and invalidate cache after writes.
- Batch by default:
_read_group, batchcreate, recordset-aware loops, and query-count checks catch most regressions. - Keep real invariants on models, not only in
onchange, cron wrappers, or controllers. - Before shipping, read best-practices-odoo-19-backend.
Cross-Skill Guidance
- Use the odoo router when the request is broad, ambiguous, or spans multiple Odoo domains.
- Use the odoo-frontend skill when the task is primarily web-client JavaScript, views, widgets, arch XML, or frontend assets.
- Use the odoo-javascript-testing skill when the task is Hoot, web test helpers, mock-server work, or frontend JS testing internals.
Source: basaltbytes/skills — distributed by TomeVault.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review