farmos-workforce

# FarmOS Workforce

Employee profiles, time clock, skills tracking, employee requests, and team calendar.

## When to Use This

**What this skill handles:** Time clock (clock in/out), schedules, availability, time-off requests, certifications, employee profiles, overtime tracking, and payroll exports.

**Trigger phrases:** "I need [day] off", "who's working", "schedule", "clock in/out", "who's clocked in?", "overtime this week?", "any pending time-off requests?", "employee list", "CDL certifications"

**What this does NOT handle:** Task assignments or work orders (use farmos-tasks), equipment scheduling or maintenance (use farmos-equipment), pay rates or financial compensation questions (restricted to admin only via farmos-finance).

**Minimum viable input:** Any mention of schedule, availability, time off, or who is working. "I need Friday off" is enough.

## Data Completeness

1. **Always state the count** of employees, time entries, or requests returned: "Found 8 active employees" or "12 time entries this pay period."
2. **Time entry queries are date-bounded** — always include `start_date` and `end_date` parameters to get the full picture for the requested period.
3. **If an endpoint fails**, report it — don't silently present empty results as "no employees" or "no time entries."
4. **For payroll exports**, verify the date range covers the full pay period before exporting.

## Authentication

This skill accesses protected FarmOS endpoints that require a JWT token.

**To get a token:**
```bash
TOKEN=$(~/clawd/scripts/farmos-auth.sh manager)
```

**Role mapping:** Check `~/.clawdbot/farmos-users.json` for the sender's role.
- **admin/manager:** Can see all employee data, hours, payroll info.
- **employee:** Can only see own profile and time entries. Do NOT use a manager token for employee queries — use the employee token so the API scopes correctly.

## API Base

http://100.102.77.110:8006

## Integration Endpoints (No Auth)

### Employee List (for assignments)
GET...