Odoo 14
Use when creating, reviewing, migrating, or debugging Odoo 14.0 addons, especially OCA-style addons that need 14.0 ORM, view, asset, security, testing, or migration guidance.From its SKILL.md
npx -y skills add wpmoo-org/odoo-skills --skill odoo-14Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
- runs commandsInstructs the agent to run 2 commands, including `node skills/odoo-14/scripts/validate-addon.mjs /path/to/addon` and 1 more.
SKILL.md
2.3 KB, 517 tokens by cl100k_base, as published. Nobody here has run it
Odoo 14 Development Skill
Use this skill when creating, reviewing, migrating, or debugging Odoo 14.0 addons, especially OCA-style addons.
First Steps
- Confirm the target branch, dependency policy, and whether the addon follows OCA rules.
- Read
references/official-sources.mdfor official Odoo 14 and OCA sources. - Pick the focused reference files for the task:
references/module-backend-security.mdreferences/ui-frontend.mdreferences/testing-quality-oca.mdreferences/porting-upgrade.md
- Check local repository conventions before adding new patterns.
Version Rules
- Target branch names and manifest versions must use
14.0. - XML list views use
<tree>, not<list>. - Action
view_modevalues usetree,form, notlist,form. attrsandstatesare valid Odoo 14 view modifier mechanisms.- Use Odoo 14 legacy JavaScript and asset patterns. Do not use Odoo 15+
manifest
assetsbundles as the default. - Do not add Odoo 17+ view modifier syntax, Odoo 18+ HOOT patterns, or Odoo 19 ORM-only APIs unless a compatibility layer exists.
- Follow OCA metadata, linting, README fragment, migration, and test conventions for OCA-style addons.
Development Checklist
- Keep manifests explicit and versioned as
14.0.x.y.z. - Declare
baseexplicitly independsunless the repository has a stricter convention. - Use
@api.model_create_multifor create overrides. - Treat recordsets as multi-record unless
ensure_one()is intentional. - Use ACLs, record rules, and field
groupsfor security. - Keep XML data ordered because XML operations are sequential.
- Use legacy web bundle inheritance and
odoo.defineJavaScript patterns. - Write focused tests and tag install-time or post-install tests deliberately.
Validation
Run the bundled lightweight validator on an addon path before final review:
node skills/odoo-14/scripts/validate-addon.mjs /path/to/addon
Then run the repository's normal OCA checks, typically pre-commit hooks,
pylint-odoo --valid-odoo-versions=14.0, and Odoo tests with the right
database and --test-tags.
What ships with it: 6 files
10.3 KB alongside SKILL.md, 1 of them executable
references/
- module-backend-security.md2.3 KB
- official-sources.md2.1 KB
- porting-upgrade.md1.2 KB
- testing-quality-oca.md1.3 KB
- ui-frontend.md1.4 KB
scripts/
- validate-addon.mjsruns2.0 KB