Stats

Actions

Available In

Tags

Generic Agent

With Odoo Skills

Guesses the Odoo version from memory

Detects version from branch, manifests, docs, config, or local source

Treats Odoo like normal Python + XML

Checks ORM, manifests, security CSVs, record rules, views, assets, tests, and version-specific APIs

Suggests commands that may touch the wrong database

Reads local setup docs/base command and asks before database-touching commands

Misses multi-company and portal/public exposure

Reviews groups, ACLs, record rules, sudo(), domains, and company isolation together

Mixes migration cleanup with feature changes

Keeps OCA migration compatibility work separate from behavior changes

Adds code without proving behavior

Writes Odoo tests at the ORM, form, access, controller, report, or mocked integration seam

Uses generic frontend advice

Routes OWL work through component, template, reactivity, props, assets, and migration guidance

Without Odoo Skills

With Odoo Skills

Adds a controller and calls sudo() to fetch the record

Asks which model/report, confirms portal ownership rule, checks auth, CSRF, access rights, record rules, and whether sudo() is safe

Puts the route in any controller file

Inspects existing controller structure and route naming conventions

Returns a PDF if the ID exists

Verifies the current user can access that record and cannot enumerate others

Skips verification

Traces route -> model -> report flow and proposes a portal/controller test or realistic user access check before running commands

Odoo Skills

Agent skills for Odoo engineering plus generic grilling, architecture review, documentation-aware planning, and codebase orientation.

What Is This?
Why Use It?
Quick Start
Real-World Example
Skills
Project Structure
Recommended Environment
How It Works
Designed For
Deliberately Out Of Scope
Stats

What Is This?

Odoo Skills is an Odoo-focused skill pack with a small set of generic engineering workflows for AI coding agents.

Odoo work is full of sharp edges: version-specific ORM APIs, XML loading order, record rules, sudo() boundaries, multi-company behavior, asset bundles, OWL version differences, and OCA migration conventions. Generic agents regularly miss those details.

This repo gives your agent a practical operating manual: what to inspect, what to ask, what not to run without confirmation, and which Odoo-specific or architectural risks to check before claiming a task is done.

Why Use It?

Generic Agent	With Odoo Skills
Guesses the Odoo version from memory	Detects version from branch, manifests, docs, config, or local source
Treats Odoo like normal Python + XML	Checks ORM, manifests, security CSVs, record rules, views, assets, tests, and version-specific APIs
Suggests commands that may touch the wrong database	Reads local setup docs/base command and asks before database-touching commands
Misses multi-company and portal/public exposure	Reviews groups, ACLs, record rules, `sudo()`, domains, and company isolation together
Mixes migration cleanup with feature changes	Keeps OCA migration compatibility work separate from behavior changes
Adds code without proving behavior	Writes Odoo tests at the ORM, form, access, controller, report, or mocked integration seam
Uses generic frontend advice	Routes OWL work through component, template, reactivity, props, assets, and migration guidance

Quick Start

Install directly with npx from GitHub:

npx github:mart337i/odoo-skills

Install only one target:

npx github:mart337i/odoo-skills --target opencode
npx github:mart337i/odoo-skills --target claude

After publishing to npm, the package can also be run as:

npx @mart337i/odoo-skills

The installer copies all skills into both ~/.claude/skills and ~/.config/opencode/skills by default. Existing skills with the same names are moved into a timestamped .backup-odoo-skills-* folder before replacement.

For local development, clone the repo:

git clone https://github.com/mart337i/odoo-skills.git
cd odoo-skills

Then symlink into Claude-style skills:

./scripts/link-skills.sh

Restart or reload your agent so it picks up the new skill list.

Real-World Example

Prompt:

Add a portal endpoint that lets customers download a PDF report for their own records.

Without Odoo Skills	With Odoo Skills
Adds a controller and calls `sudo()` to fetch the record	Asks which model/report, confirms portal ownership rule, checks `auth`, CSRF, access rights, record rules, and whether `sudo()` is safe
Puts the route in any controller file	Inspects existing controller structure and route naming conventions
Returns a PDF if the ID exists	Verifies the current user can access that record and cannot enumerate others
Skips verification	Traces route -> model -> report flow and proposes a portal/controller test or realistic user access check before running commands

The point is not more ceremony. The point is fewer security bugs, fewer broken module updates, and less cleanup after the agent "helped."

odoo-skills

Popularity

What's Inside

Confidence

README

Odoo Skills

Table Of Contents

What Is This?

Why Use It?

Quick Start

Real-World Example

Skills

Similar Plugins

caveman

frontend-design

ui-design

claude-mem

marketing-skills

nanobanana

Odoo Skills

Table Of Contents

What Is This?

Why Use It?

Quick Start

Real-World Example

Skills

Popularity

Health & Quality

Similar Plugins

caveman

frontend-design

ui-design

claude-mem

marketing-skills

nanobanana