mart337i/odoo-skills

---

Table Of Contents

• 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?

---

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.

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

---

Skills

---

Project Structure

odoo-skills/
├── AGENTS.md
├── CLAUDE.md
├── README.md
├── bin/
│   └── odoo-skills.js
├── package.json
├── scripts/
│   └── link-skills.sh
└── skills/
    ├── grill-me/
    ├── grill-with-docs/
    ├── improve-codebase-architecture/
    ├── odoo/
    ├── odoo-17.0/
    ├── odoo-18.0/
    ├── odoo-19.0/
    ├── odoo-20.0/
    ├── odoo-code-review/
    ├── odoo-code-tracer/
    ├── odoo-grill-me/
    ├── odoo-idea-gates/
    ├── odoo-migration/
    ├── odoo-owl/
    ├── odoo-report-design/
    ├── odoo-report-migration/
    ├── odoo-test-writer/
    ├── odoo-website/
    ├── odoo-web-security/
    ├── odoo-web-testing/
    └── zoom-out/

There are no bucket folders. Skills live directly under skills/ so they are easy to link into different agent environments.

---

Recommended Environment

If your Odoo source checkout is outside the project being edited, expose it so agents can inspect framework code instead of relying on memory:

export ODOO_SOURCE=/path/to/odoo

You can also expose your local Odoo command and setup docs:

export ODOO_BASE_COMMAND="/path/to/odoo/odoo-bin -c /path/to/odoo.conf --addons-path=/path/to/addons"
export ODOO_TOOL_README=/path/to/local-development/README.md

ODOO_BASE_COMMAND is the base command agents should inspect before proposing install/update/test commands. ODOO_TOOL_README points to local setup documentation agents should read before using project-specific tooling.

Put those exports in your shell profile if you want them available in every agent session.

---

How It Works

flowchart LR
    A[Developer prompt] --> B[AI agent]
    B --> C[Odoo Skills]
    C --> D[Repo inspection]
    C --> E[Odoo conventions]
    C --> F[Security and migration guardrails]
    D --> G[Safer Odoo change]
    E --> G
    F --> G

The skills push agents toward a simple discipline:

1. Detect the Odoo version and repo shape.
2. Use version-specific references for Odoo 17, 18, 19, and 20 when detailed API guidance is needed.
3. Read manifests, models, views, security, assets, tests, and docs before editing.
4. Trace execution paths when behavior depends on controllers, buttons, cron jobs, overrides, or side effects.
5. Write tests at the Odoo behavior seam: ORM, form, access, workflow, controller, report, or mocked integration.
6. Use local Odoo source and setup docs when available.
7. Ask before running commands that touch databases or services.
8. Verify at the Odoo behavior seam, not just with generic static checks.

---

Designed For

• Odoo addon development.
• Odoo module and app idea validation before implementation.
• OCA repositories.
• OCA module migrations between major Odoo versions.
• QWeb/PDF report design, review, and visual-preservation migrations.
• OWL/web client frontend work.
• Odoo code reviews and architecture checks.
• Odoo test writing for custom modules.
• Odoo execution tracing and impact analysis.
• Odoo 17, 18, and 19 version-specific reference lookup.
• Odoo 20 version-specific reference lookup.
• Generic plan grilling, documentation-aware design work, architecture review, and codebase orientation.
• Agents working in unfamiliar Odoo codebases.
• Odoo website, portal, public controller, browser security, and web testing work.

---

Deliberately Out Of Scope

OpenUpgrade workflows are not covered. The migration skill is for normal OCA module migration and [MIG] pull request preparation.

---

Stats

---