Odoo logo

Odoo

Community
mart337i
odoo

Odoo engineering workflows for addon development, codebase exploration, debugging, architecture/refactor review, manifest/docs sync, and routing to migration work. Use when the user mentions Odoo, addons, modules, manifests, models, XML views, security CSVs, record rules, Odoo shell, OWL/QWeb/assets, or when an Odoo codebase is detected.

Overview

Publishermart337i
Repositoryodoo-skills
Skill nameodoo
Stars
61
Forks
15
Bundled files
6
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 6 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by mart337i on GitHub. Read the source before you install it.

Installation

Install the Odoo AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/mart337i/odoo-skills/tree/main/skills/odoo
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/mart337i/odoo-skills.git /tmp/odoo-skills
mkdir -p .claude/skills
cp -r /tmp/odoo-skills/skills/odoo .claude/skills/odoo
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Odoo in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Odoo on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Odoo is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Odoo

Use this skill only for Odoo work. For OCA module migration or major-version addon ports, route to odoo-migration.

First Move

Explore before asking. Inspect the repo for Odoo signals: __manifest__.py, odoo-bin, addons/, models/, views/, security/ir.model.access.csv, controllers/, static/src/, and project docs.

Before version-sensitive changes, detect the target Odoo version from branch names, manifests, docs, dependencies, or config. If the version is not discoverable, ask. If $ODOO_SOURCE is set, inspect it for framework behavior instead of guessing.

Before running Odoo update/test commands, inspect likely commands from repo docs/config. If $ODOO_TOOL_README is set, read it for local tooling. If $ODOO_BASE_COMMAND is set, use it as the starting point for proposed Odoo commands. Then ask the user to confirm before running commands that touch a database or local service.

Route The Task

  • Stress-test an Odoo plan/design before implementation: use odoo-grill-me.
  • Build or change addon behavior: use DEVELOPMENT.md.
  • Understand an unfamiliar Odoo codebase: use EXPLORATION.md.
  • Debug broken Odoo behavior: use DEBUGGING.md.
  • Trace a concrete execution path through controllers, buttons, cron jobs, model methods, overrides, computes, onchanges, constraints, or side effects: use odoo-code-tracer.
  • Hunt for Odoo architecture/refactor opportunities: use ARCHITECTURE.md.
  • Sync manifest/docs with implemented behavior: use MANIFEST-DOCS.md.
  • Build, review, debug, or migrate Odoo OWL frontend components: use odoo-owl.
  • Build or change Odoo website, portal, public pages, QWeb integration, or website assets: use odoo-website.
  • Review public/portal controllers, browser-facing data, tokens, HTML output, or web trust boundaries: use odoo-web-security.
  • Test Odoo HTTP routes, portal/public access, browser flows, assets, or JavaScript behavior: use odoo-web-testing.
  • Design or review QWeb HTML/PDF report layout, print CSS, paper formats, pagination, or report assets: use odoo-report-design.
  • Migrate QWeb/PDF reports while preserving their visual output across Odoo versions: use odoo-report-migration together with odoo-migration.
  • Review Odoo code for correctness, security, performance, tests, migrations, manifests, and official coding guidelines: use odoo-code-review.
  • Create or improve Odoo tests using TransactionCase, HttpCase, Form helper, tags, mocks, access tests, workflow tests, or test coverage patterns: use odoo-test-writer.
  • Migrate an OCA addon between Odoo major versions: use odoo-migration.
  • Need detailed known-version guidance: use odoo-17.0, odoo-18.0, odoo-19.0, or odoo-20.0.

Always Apply

Use the compact conventions in CONVENTIONS.md. Keep changes small and idiomatic. Include a security pass when models, views, controllers, workflows, or access behavior change. For business data modules, lightly check multi-company behavior: company_id, defaults, domains, record rules, and cross-company reads/writes.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Odoo AI skill do?

Odoo engineering workflows for addon development, codebase exploration, debugging, architecture/refactor review, manifest/docs sync, and routing to migration work. Use when the user mentions Odoo, addons, modules, manifests, models, XML views, security CSVs, record rules, Odoo shell, OWL/QWeb/assets, or when an Odoo codebase is detected.

Why use Odoo on TypingMind?

Because you install it once and use it with any model. Odoo is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Odoo in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/mart337i/odoo-skills/tree/main/skills/odoo. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Odoo?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Odoo?

As many as you like. As long as a model supports skills, you can use Odoo with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Odoo AI skill free?

It is published on GitHub by mart337i. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇