← ClaudeAtlas

timesheetlisted

Track time and manage projects, tasks, absences, contracts, expenses, todos, and team data in timesheet.io, with the Timesheet connector's tools when they are available and the @timesheet/cli command-line tool otherwise
timesheetIO/timesheet-plugin · ★ 0 · AI & Automation · score 78
Install: claude install-skill timesheetIO/timesheet-plugin
# Timesheet Skill Control [timesheet.io](https://timesheet.io) through the Timesheet connector or from the shell. Before you change or delete an existing record, read it first. Starting the timer and adding a time entry need no read first. ## Connector or CLI Check your tools first. When the Timesheet connector's tools are available, use them instead of the CLI: they need no install or login, and they also work in web and desktop apps, where the CLI usually isn't installed. - Tool names follow `<area>_<action>` in the singular, such as `timer_start`, `task_list`, `project_create`, and `absence_approve`. Hosts may add a prefix, such as `mcp__timesheet__timer_start`. The CLI's `show` is the tool's `get`. The `show_*` tools are something else: they show a card (see the next section). - Reports map to `statistics_get` for summaries (up to one year per call) and `export_generate` for xlsx, csv, or pdf exports, which it returns as a download URL. Get its `report` type from `export_report_types`. Its `title` sets the heading of a PDF export, which is the report's name otherwise. - Saved export settings are the `export_template_*` tools, and `export_from_template` runs a template for a period. - Take parameters from each tool's input schema, not from the CLI flags below. The CLI workflows further down are for the CLI: with the connector, follow the next section. Use the CLI when the connector isn't available, for local defaults (`timesheet config`), or when an export must be sav