agentleFS
actinon-comactinon-com/brass-monkey/skills/odoo-attendance/SKILL.md

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.

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
  1. Very specific:

    Mandate: Always verify the attendance_state on the hr.employee record before attempting to create a new check-in or update a check-out.

    line 14
  2. Very specific:

    Status Check: Search hr.employee to find the current attendance_state.

    line 26
  3. Very specific:

    Overtime Audit: Check the total_overtime computed field on the employee record for a historical summary.

    line 28

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 a check_in and optional check_out datetime.
  • Open Sessions: An employee can only have ONE record with an empty check_out at any time. This represents a currently "Checked In" status.
  • Mandate: Always verify the attendance_state on the hr.employee record 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_in and check_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 check overtime_status to see if extra hours require manager approval.

3. Kiosk Mode & Security

  • Authentication: In Kiosk mode, employees use a pin or barcode (on the hr.employee model) 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

  1. Status Check: Search hr.employee to find the current attendance_state.
  2. Log Review: Query hr.attendance filtered by employee_id and check_in date range.
  3. Overtime Audit: Check the total_overtime computed 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.