From unanet
Fill timesheets, view time entries, submit timesheets, create and view leave requests on Unanet. Use when user asks about timesheets, time entry, logging hours, PTO, leave requests, taking time off, viewing leave, or says "/unanet".
How this skill is triggered — by the user, by Claude, or both
Slash command
/unanet:unanetThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Manage Unanet timesheets and leave requests via the `unanet` CLI tool.
Manage Unanet timesheets and leave requests via the unanet CLI tool.
unanet must be installed. If any command fails with "command not found" or "No config found", suggest running /setup-unanet.
/unanet — View current timesheet/unanet fill 8h EERT for Wednesday and Thursday — Fill time entries/unanet submit — Submit completed timesheet/unanet I want to take off April 3rd — Create a leave request/unanet show my leave requests — View all leave requestsunanet view
Returns JSON with current timesheet state and saves a screenshot to /tmp/unanet-screenshot.png. Always show the screenshot to the user with the Read tool.
Parse the user's natural language request into structured JSON:
unanet fill --data '{"project":"EERT","hours":8,"days":["2026-03-18","2026-03-19"]}'
Field mapping:
project: Match against project names on the timesheet (partial match, case-insensitive)
hours: Number of hours per daydays: Array of ISO date strings (YYYY-MM-DD)Interpreting natural language dates:
After filling, the tool saves and takes a screenshot. Always show the screenshot to the user.
unanet submit
Only use when the user explicitly asks to submit. This is different from Save (which happens automatically after fill).
# Single leave request
unanet leave --data '{"begin":"2026-04-03","end":"2026-04-03","hours":8}'
# Batch multiple leave requests in one session (preferred for multiple dates)
unanet leave --data '[{"begin":"2026-04-03","end":"2026-04-03","hours":8},{"begin":"2026-05-15","end":"2026-05-15","hours":8}]'
Field mapping:
begin: Start date (YYYY-MM-DD)end: End date (YYYY-MM-DD), same as begin for single-day requestshours: Total hours for the leave period (8 per day typically)comments: Optional comment textsubmit: Set to true to submit for approval (default: save only)includeNonWorkDays: Set to true to include weekends (default: false)Batch leave requests: When the user requests multiple leave dates, always use a JSON array to create them all in one CLI invocation. This uses a single browser session and avoids repeated Okta logins. Each request gets its own numbered screenshot (-1.png, -2.png, etc.).
Interpreting natural language:
{"begin":"2026-04-03","end":"2026-04-03","hours":8}{"begin":"2026-04-03","end":"2026-04-04","hours":16}[{"begin":"2026-10-15","end":"2026-10-16","hours":16},{"begin":"2026-10-19","end":"2026-10-19","hours":8}] (group consecutive days into ranges)Use --no-save to preview without saving.
unanet leave-list
Returns JSON array of all current leave requests with begin/end dates, hours, status, and comments. Also saves a screenshot. Always show the screenshot to the user.
--visible — Show the browser window (useful for debugging)--no-save — Preview without saving (works with fill and leave)--screenshot PATH — Custom screenshot path (default: /tmp/unanet-screenshot.png)Read /tmp/unanet-screenshot.pngnpx claudepluginhub ericboehs/claude-plugins --plugin unanetTracks time on tasks with timers or manual entries and generates timesheet reports. Use when logging hours, starting/stopping timers, or asking 'how much time was spent?'
Manages Autotask time entries for logging hours, billing calculations, approval workflows, utilization tracking, budget validation, and integrations with tickets/projects.
Automates Harvest time tracking, project management, and invoicing via natural language commands. Log hours, manage projects/clients/tasks, and pull reports from the terminal.