Agent skill

Odoo Security Rules

by sickn33 in sickn33/agentic-awesome-skills

Expert in Odoo access control: ir.model.access.csv, record rules (ir.rule), groups, and multi-company security patterns.

MITAuto-check passedDocuments & Office

Install Odoo Security Rules

skills CLI

$ npx skills add sickn33/agentic-awesome-skills --skill odoo-security-rules -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install sickn33/agentic-awesome-skills odoo-security-rules --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/odoo-security-rules .claude/skills/odoo-security-rules && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "odoo-security-rules" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/odoo-security-rules into .claude/skills/odoo-security-rules/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "odoo-security-rules", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/odoo-security-rules

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add sickn33/agentic-awesome-skills --skill odoo-security-rules -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install sickn33/agentic-awesome-skills odoo-security-rules --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/odoo-security-rules .agents/skills/odoo-security-rules && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "odoo-security-rules" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/odoo-security-rules into .agents/skills/odoo-security-rules/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "odoo-security-rules", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add sickn33/agentic-awesome-skills --skill odoo-security-rules -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install sickn33/agentic-awesome-skills odoo-security-rules --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/odoo-security-rules .cursor/skills/odoo-security-rules && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "odoo-security-rules" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/odoo-security-rules into .cursor/skills/odoo-security-rules/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "odoo-security-rules", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/sickn33/agentic-awesome-skills.git --path skills/odoo-security-rules

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add sickn33/agentic-awesome-skills --skill odoo-security-rules -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install sickn33/agentic-awesome-skills odoo-security-rules --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/odoo-security-rules .gemini/skills/odoo-security-rules && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "odoo-security-rules" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/odoo-security-rules into .gemini/skills/odoo-security-rules/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "odoo-security-rules", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install sickn33/agentic-awesome-skills odoo-security-rules

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add sickn33/agentic-awesome-skills --skill odoo-security-rules -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/odoo-security-rules .github/skills/odoo-security-rules && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "odoo-security-rules" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/odoo-security-rules into .github/skills/odoo-security-rules/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "odoo-security-rules", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add sickn33/agentic-awesome-skills --skill odoo-security-rules -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install sickn33/agentic-awesome-skills odoo-security-rules --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/odoo-security-rules .opencode/skills/odoo-security-rules && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "odoo-security-rules" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/odoo-security-rules into .opencode/skills/odoo-security-rules/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "odoo-security-rules", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: odoo-security-rules
GitHub stars: 47k
Used in: 2 other repos
Token cost: ~1.1k tokens
SKILL.md length: 371 words
Files: 1
Skills in repo: 1,394
Repo updated: Oct 6, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Expert in Odoo access control: ir.model.access.csv, record rules (ir.rule), groups, and multi-company security patterns.

Works in 3 steps: Activate: Mention @odoo-security-rules… → Generate: Get correct CSV access lines… → Debug: Paste an access error and get a…
Tasks that involve CSV and tabular files
SKILL.md covers Overview, When to Use This Skill, How It Works and Examples, plus 2 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Odoo Security Rules is an agent skill from sickn33/agentic-awesome-skills. Expert in Odoo access control: ir.model.access.csv, record rules (ir.rule), groups, and multi-company security patterns.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Documents & Office, covering CSV and tabular files and Authorization and RBAC. It works with Odoo. The repository describes itself as: AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,400+ agentic skills. Includes… The licence is MIT.

When your agent uses it

Tasks that involve CSV and tabular files
Tasks that involve Authorization and RBAC

Example prompts

“/odoo-security-rules”

Requirements

Python 3

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

Activate: Mention @odoo-security-rules and describe the access scenario.
Generate: Get correct CSV access lines and XML record rules.
Debug: Paste an access error and get a diagnosis with the fix.

What it can do on your machine

Read from SKILL.md and the folder at commit 1e53ce2. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are xml and csv).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Odoo Security Rules loads about 1.1k tokens when it runs. Until then it costs about 35 tokens; SKILL.md has 371 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~35
When it runs · the whole SKILL.md, loaded when a task matches: ~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from sickn33/agentic-awesome-skills at commit 1e53ce2, republished under its MIT licence (© sickn33). 371 words, ~1,078 tokens.

Download SKILL.mdSave it as .claude/skills/odoo-security-rules/SKILL.md (or your agent's skills folder).

name: odoo-security-rules
description: Expert in Odoo access control: ir.model.access.csv, record rules (ir.rule), groups, and multi-company security patterns.
risk: safe
source: self
date_added: 2026-09-04

Odoo Security Rules

Overview

Security in Odoo is managed at two levels: model-level access (who can read/write which models) and record-level rules (which records a user can see). This skill helps you write correct ir.model.access.csv entries and ir.rule domain-based record rules.

When to Use This Skill

Setting up access rights for a new custom module.
Restricting records so users only see their own data or their company's data.
Debugging "Access Denied" or "You are not allowed to access" errors.
Implementing multi-company record visibility rules.

How It Works

Activate: Mention @odoo-security-rules and describe the access scenario.
Generate: Get correct CSV access lines and XML record rules.
Debug: Paste an access error and get a diagnosis with the fix.

Examples

Example 1: ir.model.access.csv

csv

id,name,model_id:id,group_id:id,perm_read,perm_write,perm_create,perm_unlink
access_hospital_patient_user,hospital.patient.user,model_hospital_patient,base.group_user,1,0,0,0
access_hospital_patient_manager,hospital.patient.manager,model_hospital_patient,base.group_erp_manager,1,1,1,1

Note: Use base.group_erp_manager for ERP managers, not base.group_system — that group is reserved for Odoo's technical superusers. Always create a custom group for module-specific manager roles:
xml
<record id="group_hospital_manager" model="res.groups">
    <field name="name">Hospital Manager</field>
    <field name="category_id" ref="base.module_category_hidden"/>
</record>

Example 2: Record Rule — Users See Only Their Own Records

xml

<record id="rule_hospital_patient_own" model="ir.rule">
    <field name="name">Hospital Patient: Own Records Only</field>
    <field name="model_id" ref="model_hospital_patient"/>
    <field name="domain_force">[('create_uid', '=', user.id)]</field>
    <field name="groups" eval="[(4, ref('base.group_user'))]"/>
    <field name="perm_read" eval="True"/>
    <field name="perm_write" eval="True"/>
    <field name="perm_create" eval="True"/>
    <field name="perm_unlink" eval="False"/>
</record>

Important: If you omit <field name="groups">, the rule becomes global and applies to ALL users, including admins. Always assign a group unless you explicitly intend a global restriction.

Example 3: Multi-Company Record Rule

xml

<record id="rule_hospital_patient_company" model="ir.rule">
    <field name="name">Hospital Patient: Multi-Company</field>
    <field name="model_id" ref="model_hospital_patient"/>
    <field name="domain_force">
        ['|', ('company_id', '=', False),
               ('company_id', 'in', company_ids)]
    </field>
    <field name="groups" eval="[(4, ref('base.group_user'))]"/>
</record>

Show full SKILL.md (168 more words)Show less

Best Practices

✅ Do: Start with the most restrictive access and open up as needed.
✅ Do: Use company_ids (plural) in multi-company rules — it includes all companies the user belongs to.
✅ Do: Test rules using a non-admin user in debug mode — sudo() bypasses all record rules entirely.
✅ Do: Create dedicated security groups per module rather than reusing core Odoo groups.
❌ Don't: Give perm_unlink = 1 to regular users unless deletion is explicitly required by the business process.
❌ Don't: Leave group_id blank in ir.model.access.csv unless you intend to grant public (unauthenticated) access.
❌ Don't: Use base.group_system for module managers — that grants full technical access including server configurations.

Limitations

Does not cover field-level access control (ir.model.fields read/write restrictions) — those require custom OWL or Python overrides.
Portal and public user access rules have additional nuances not fully covered here; test carefully with base.group_portal.
Record rules are bypassed by sudo() — any code running in superuser context ignores all ir.rule entries.
Does not cover row-level security via PostgreSQL (RLS) — Odoo manages all security at the ORM layer.

Files

Just SKILL.md in skills/odoo-security-rules of sickn33/agentic-awesome-skills.

Open the folder on GitHubat commit 1e53ce2

Used in 2 other repositories

We found 15 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in sickn33/agentic-awesome-skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Odoo Security Rules next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Odoo Security Rules compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Odoo Security Rules this skillsickn33/agentic-awesome-skills	47k	2 repos	~1.1k	Automated safety check: Pass	MIT	today
Issue Driven Workflowappautomaton/agent-designer	131	—	~1.6k	Automated safety check: Warn	None	24 days ago
Scenario Admin Analyticsscenario-labs/skills	898	—	~2.9k	Automated safety check: Pass	MIT	today
Instrument Data To Allotropeaws-samples/amazon-bedrock-agents-healthcare-lifesciences	274	2 repos	~2.7k	Automated safety check: Pass	Apache-2.0	5 days ago
Sector Analysttradermonty/claude-trading-skills	3k	1 repos	~2.3k	Automated safety check: Pass	MIT	yesterday
Cliare Artifact Reviewmodiqo/cliare	469	—	~2.4k	Automated safety check: Pass	Apache-2.0	2 mo ago

Similar skills

Issue Driven Workflow
appautomaton/agent-designer
Turn a large task into a persistent plan file and a trackable Issue CSV (local files, not an external issue tracker), then execute the issues autonomously with per-row status updates.
131 GitHub stars~1.6k tokensUpdated 24 days ago
Documents & OfficeAuto-check: warnings
Scenario Admin Analytics
scenario-labs/skills
A skill your agent uses when answering Scenario admin analytics questions about Creative Unit consumption, most-used models, usage by user or project, AI adoption observability, cached usage data…
898 GitHub stars~2.9k tokensUpdated today
Documents & OfficeAuto-check passed
Instrument Data To Allotrope
aws-samples/amazon-bedrock-agents-healthcare-lifesciences
Official
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV.
274 GitHub starsUsed in 2 repos~2.7k tokens
Documents & OfficeAuto-check passed
Sector Analyst
tradermonty/claude-trading-skills
This skill should be used when analyzing sector rotation patterns and market cycle positioning.
3k GitHub starsUsed in 1 repo~2.3k tokens
Documents & OfficeAuto-check passed
Cliare Artifact Review
modiqo/cliare
A skill your agent uses when reviewing a CLIARE measurement artifact directory, explaining score changes, triaging issues, finding evidence, or proposing CLI remediation work from artifact-map.json…
469 GitHub stars~2.4k tokensUpdated 2 mo ago
Documents & OfficeAuto-check passed
Convert File
duckdb/duckdb-skills
Official
Convert any data file to another format: CSV, Parquet, JSON, Excel, GeoJSON, and more.
599 GitHub starsUsed in 1 repo~720 tokens
Documents & OfficeAuto-check: notes

Questions about Odoo Security Rules

What does Odoo Security Rules do?

Expert in Odoo access control: ir.model.access.csv, record rules (ir.rule), groups, and multi-company security patterns. Odoo Security Rules is an agent skill from sickn33/agentic-awesome-skills.rule), groups, and multi-company security patterns.

When should I use Odoo Security Rules?

Odoo Security Rules fits situations like: tasks that involve CSV and tabular files; tasks that involve Authorization and RBAC.

How do I install Odoo Security Rules in Claude Code?

Run `npx skills add sickn33/agentic-awesome-skills --skill odoo-security-rules -a claude-code`. Or copy the skill folder (skills/odoo-security-rules in sickn33/agentic-awesome-skills) into .claude/skills/odoo-security-rules in your project. Claude Code loads it when a task matches its description.

How do I install Odoo Security Rules in Codex?

Run `npx skills add sickn33/agentic-awesome-skills --skill odoo-security-rules -a codex`. Or copy the skill folder (skills/odoo-security-rules in sickn33/agentic-awesome-skills) into .agents/skills/odoo-security-rules in your project. Codex loads it when a task matches its description.

Can I use Odoo Security Rules in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sickn33/agentic-awesome-skills --skill odoo-security-rules -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/odoo-security-rules, .gemini/skills/odoo-security-rules, .github/skills/odoo-security-rules and .opencode/skills/odoo-security-rules in your project.

What does Odoo Security Rules need to run?

SKILL.md names no scripts, command-line tools or credentials: Odoo Security Rules is instructions for the agent only. Our summary lists: Python 3.

Does Odoo Security Rules access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Odoo Security Rules safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Odoo Security Rules use?

Odoo Security Rules is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Odoo Security Rules use?

About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Odoo Security Rules?

Skills that share tags, products or a category with Odoo Security Rules: Issue Driven Workflow (appautomaton/agent-designer, 131 stars), Scenario Admin Analytics (scenario-labs/skills, 898 stars), Instrument Data To Allotrope (aws-samples/amazon-bedrock-agents-healthcare-lifesciences, 274 stars) and Sector Analyst (tradermonty/claude-trading-skills, 3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Odoo Security Rules?

sickn33 (a GitHub user) maintains it in sickn33/agentic-awesome-skills, which has 47,304 GitHub stars. The repository holds 1,394 skills in this directory. The repository was last updated on October 6, 2026.

Source: sickn33/agentic-awesome-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Odoo Security Rules

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Odoo Security Rules

Overview

When to Use This Skill

How It Works

Examples

Example 1: ir.model.access.csv

Example 2: Record Rule — Users See Only Their Own Records

Example 3: Multi-Company Record Rule

Best Practices

Limitations

Files

Used in 2 other repositories

Compare with similar skills

Similar skills

More from sickn33/agentic-awesome-skills

Related

Questions about Odoo Security Rules