odoo-hr
Skill2 starsChanged 3 months agoMITView on GitHub
MANDATORY for Employees (hr.employee) and Departments (hr.department). Expertise in Odoo's human resources and org structure.
In this repository30 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- odoo-attendanceSkill
- odoo-crmSkill
- odoo-dashboardsSkill
- odoo-data-opsSkill
- odoo-devSkill
- odoo-documentsSkill
- odoo-field-serviceSkill
- odoo-financeSkill
- odoo-frontdeskSkill
- odoo-get-startedSkill
- odoo-helpdeskSkill
- odoo-introspectorSkill
- odoo-inventorySkill
- odoo-knowledgeSkill
- odoo-mrpSkill
- odoo-plmSkill
- odoo-productsSkill
- odoo-projectsSkill
- odoo-purchasingSkill
- odoo-qualitySkill
- odoo-relationsSkill
- odoo-reportsSkill
- odoo-salesSkill
- odoo-securitySkill
- odoo-spreadsheetsSkill
- odoo-uxSkill
- odoo-websiteSkill
- odoo-worksheetsSkill
- odoo-workspaceSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 0 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
Mandate: When creating an employee, always verify if a res.users record already exists to ensure proper linking.
- Very specific: line 19
Reporting: Every employee has a Manager (parent_id).
- Very specific: line 28
Locate: Search hr.employee by name or work_email.
- Very specific: line 29
Structure: Check parent_id and department_id to understand the employee's place in the org chart.
- Very specific: line 30
Status: Verify the attendance_state (if Attendance is used) and the contract_id status.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Skill: Odoo Human Resources (HR)
This skill provides the agent with functional expertise in Odoo's HR module, covering Employee management, Departmental structures, and Employment contracts.
Core Mandates
1. The Internal Identity (The Holy Trinity)
In Odoo, an internal person is represented by three linked records:
- Employee (
hr.employee): The operational record (Manager, Department, Job). - User (
res.users): The system access record (Login, Permissions). - Partner (
res.partner): The communication record (Email, Phone, Address). - Mandate: When creating an employee, always verify if a
res.usersrecord already exists to ensure proper linking.
2. Organizational Hierarchy
- Reporting: Every employee has a Manager (
parent_id). This field dictates the approval flow for Timesheets, Time Off, and Expenses. - Departments: Employees are grouped into Departments (
hr.department). Departments can be nested (e.g., "R&D / Software").
3. Contracts & Compliance
- Contract (
hr.contract): The legal anchor. Dictates the Wage, Working Schedule, and Start/End Dates. - States:
draft(New) ->open(Running) ->close(Expired). - Mandate: An employee must have a
runningcontract for many Odoo features (like Payroll or specific Attendance rules) to function correctly.
4. Search Workflow
- Locate: Search
hr.employeebynameorwork_email. - Structure: Check
parent_idanddepartment_idto understand the employee's place in the org chart. - Status: Verify the
attendance_state(if Attendance is used) and thecontract_idstatus.
Available Resources
hr-logic.md: Deep-dive into Working Schedules, Org Chart behavior, and Onboarding/Offboarding workflows.hr-fields.json: Dense technical map of fields for Employee, Department, Job, and Contract models.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

