From tim
Log, view, and manage work hours using the 'tim' CLI tool. Use this skill whenever the user wants to register hours, check what they've logged, log time on a project, track hours for a client, or do anything related to time tracking — even if they just say "log hours", "føre timer", "I worked today", or mention a project name alongside time.
How this skill is triggered — by the user, by Claude, or both
Slash command
/tim:log-hoursThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use the `tim` CLI to log and manage work hours. Act immediately — never ask unnecessary questions.
Use the tim CLI to log and manage work hours. Act immediately — never ask unnecessary questions.
When the user wants to log hours:
tim write (logs 7.5h to default project, today)tim projects to find the ID, then tim write -p <projectId>tim write 3,5 or tim write -p ANE1006 3,5tim write --help for the date flag syntaxtim write command separately (not chained with &&) to avoid timeoutsAfter every write operation (logging hours, updating entries), always run tim ls and display the result as a table so the user can see the full week overview:
tim ls
# Log default hours (7.5h) on default project
tim write -y
# Log hours on a specific project
tim projects # find project IDs
tim write -y -p <projectId> # log 7.5h on that project
# Log custom hours
tim write -y 3,5 # 3.5h on default project
tim write -y -p ANE1006 3,5 # 3.5h on specific project
# NOTE: Only `tim write` supports -y/--yes. Other commands are non-interactive.
# View logged hours
tim ls # current week
tim ls --range PreviousWeek
tim ls --range PreviousMonth
# Valid --range values: SingleDay, CurrentWeek, PreviousWeek, CurrentMonth, PreviousMonth
# Manage default project
tim get-default
tim set-default <projectId>
# Week overview for a client
tim emp ls -c "Client Name" --ids | tim ls
# Project hours for a client
tim projects -c "Client Name" --ids | tim projects time -r PreviousMonth
# Download CSV for invoicing
tim projects -c "Client Name" --ids | tim reports project-employee-hours -r previousmonth
tim curl er et spørre-/utforskingsverktøy. Bruk det aldri til å føre timer, oppdatere oppføringer eller gjøre noen form for skriveoperasjoner — selv om du ikke finner et passende native command.
tim curl is strictly for reading and exploring data. Never use it to create, update, or delete entries.
# Fetch the OpenAPI spec — use this to discover available tables, columns, and RPC functions
tim curl '/'
# Direct PostgREST queries (GET/read only)
tim curl '/employees?select=first_name,last_name'
tim curl -x post '/rpc/employees_on_projects' --data '{"from_date":"2025-11-01","to_date":"2025-11-30"}'
When the user asks for something tim doesn't support natively: fetch tim curl '/' first to explore the schema, then construct the appropriate read query. If the task requires writing data, tell the user that this operation is not supported.
| Name | Description |
|---|---|
absence | Employee absence entries |
absence_reasons | Valid absence reason types |
available_projects | Projects available for time entry |
customers | Customers/clients |
employees | Employee records |
expense | Expense entries |
holidays | Public holidays |
projects | All projects |
staffing | Staffing allocations |
staffing_per_week | Weekly staffing view |
time_entry | Raw time entries |
timelock_events | Hour lock events |
vacation_days | Vacation day records |
vacation_days_by_year | Vacation days grouped by year |
vacation_days_earnt | Earned vacation days |
vacation_days_spent | Spent vacation days |
write_off | Write-off entries |
| Function | Description |
|---|---|
employees_on_projects | Employees on projects in a date range |
accumulated_time_tracking | Accumulated time tracking per employee |
hours_per_employee | Hours logged per employee |
hours_per_project | Hours logged per project |
time_tracking_status | Time tracking status per employee |
time_tracking_status_by_week | Weekly time tracking status |
unregistered_days | Days with missing time entries |
get_periodic_report | Periodic hours report |
projects_info_for_employee_in_period | Projects for an employee in a period |
who_am_i | Returns the currently authenticated employee |
kpi_fg | Billable rate KPI |
staffing_and_billing_overview | Staffing vs billing overview |
tim not found → tell user to install it via Homebrew:
brew tap blankoslo/tools [email protected]:blankoslo/homebrew-tools.git
brew install blankoslo/tools/tim
tim projects and ask user to picktim loginnpx claudepluginhub blankoslo/claude-marketplace --plugin timTracks 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?'
Automates Clockify time tracking via natural language: create/delete time entries, query history, manage workspaces, and audit team activity.
Time tracking, worklogs, and time reports. TRIGGERS: 'log time', 'time spent on', 'log hours', 'log work', 'worklog', 'time tracking', 'timesheet', 'how much time', 'time logged', 'time report', 'export timesheet', 'set estimate', 'remaining estimate', 'original estimate'. Use for time-related queries and operations on issues. NOT FOR: SLA tracking (use jira-jsm), date-based issue searches (use jira-search), issue field updates unrelated to time (use jira-issue).