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

odoo-frontdesk

Skill2 starsChanged 3 months agoMITView on GitHub

Functional expertise in Odoo's Frontdesk application, covering visitor management, reception check-ins, and host notifications.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check-In: When a visitor arrives, update their state and capture the check_in time.

    line 13
  2. Very specific:

    The Host (host_ids): Every visitor is usually seeing one or more Employees.

    line 17
  3. Very specific:

    Mandate: Always verify the host_ids are set to ensure the correct internal staff are alerted.

    line 19
  4. Very specific:

    Verification: Before creating a new visitor, search for an existing res.partner using name or email.

    line 26
  5. Distinctive:

    Duplicate Prevention: Avoid creating multiple visitor records for the same planned appointment.

    line 27

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

This skill provides the agent with functional expertise in Odoo's Frontdesk application, covering visitor management, reception check-ins, and host notifications.

Core Mandates

1. Visitor Lifecycle

  • States: planned (Upcoming appointment) -> checked_in (Visitor is on-site) -> checked_out (Visitor has left).
  • Check-In: When a visitor arrives, update their state and capture the check_in time.
  • Check-Out: Recording the check_out time is mandatory for accurate fire-safety and presence logs.

2. Host & Notifications

  • The Host (host_ids): Every visitor is usually seeing one or more Employees.
  • Notifications: Upon check-in, Odoo can automatically notify the host via Discuss, Email, or SMS based on the Station configuration.
  • Mandate: Always verify the host_ids are set to ensure the correct internal staff are alerted.

3. Stations & Kiosks

  • Station (frontdesk.frontdesk): Represents a physical reception point or tablet.
  • Configuration: Stations dictate what information is required (e.g., Company, Phone, Email) and whether drinks are offered.

4. Search & Data Integrity

  • Verification: Before creating a new visitor, search for an existing res.partner using name or email. Linking to a partner record provides a richer history of interactions.
  • Duplicate Prevention: Avoid creating multiple visitor records for the same planned appointment.

Available Resources

  • frontdesk-logic.md: Deep-dive into Notification routing, Station settings, and Pre-Registration.
  • frontdesk-fields.json: Dense technical map of fields for Visitor and Frontdesk models.

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.