odoo-attendance
Skill2 starsChanged 3 months agoMITView on GitHub
Functional expertise in Odoo's Attendance module, covering check-in/out logs, working hour verification, and overtime management.
In this repository30 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- odoo-crmSkill
- odoo-dashboardsSkill
- odoo-data-opsSkill
- odoo-devSkill
- odoo-documentsSkill
- odoo-field-serviceSkill
- odoo-financeSkill
- odoo-frontdeskSkill
- odoo-get-startedSkill
- odoo-helpdeskSkill
- odoo-hrSkill
- 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
3 rules. About 0 are common, 0 are distinctive, and 3 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.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Mandate: Always verify the attendance_state on the hr.employee record before attempting to create a new check-in or update a check-out.
- Very specific: line 26
Status Check: Search hr.employee to find the current attendance_state.
- Very specific: line 28
Overtime Audit: Check the total_overtime computed field on the employee record for a historical summary.
≈ “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 Attendance
This skill provides the agent with functional expertise in Odoo's Attendance module, covering check-in/out logs, working hour verification, and overtime management.
Core Mandates
1. Attendance Lifecycle
- Record (
hr.attendance): A simple log with acheck_inand optionalcheck_outdatetime. - Open Sessions: An employee can only have ONE record with an empty
check_outat any time. This represents a currently "Checked In" status. - Mandate: Always verify the
attendance_stateon thehr.employeerecord before attempting to create a new check-in or update a check-out.
2. Overtime & Verification
- Worked Hours: Automatically calculated as the difference between
check_inandcheck_out. - Expected Hours: Pulled from the employee's Working Schedule (
resource.calendar) via their contract. - Overtime: Calculated as
Worked Hours - Expected Hours. The agent should checkovertime_statusto see if extra hours require manager approval.
3. Kiosk Mode & Security
- Authentication: In Kiosk mode, employees use a
pinorbarcode(on thehr.employeemodel) to authenticate. - Data Integrity: Mandate that agents do not manually create overlapping attendance records, as this will break Odoo's internal hour reporting.
4. Search Workflow
- Status Check: Search
hr.employeeto find the currentattendance_state. - Log Review: Query
hr.attendancefiltered byemployee_idandcheck_indate range. - Overtime Audit: Check the
total_overtimecomputed field on the employee record for a historical summary.
Available Resources
attendance-logic.md: Deep-dive into Overtime calculations, Kiosk configuration, and Attendance vs. Timesheets.attendance-fields.json: Dense technical map of fields for Attendance and Employee presence.
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.

