toggl-track

Installation
SKILL.md

Toggl Track

Use the API contracts and a narrow, reviewable sequence of API calls to manage the user's Toggl Track account. The Core API manages workspace data; the Reports API serves reports and exports; the Webhooks API manages event subscriptions. Do not assume that an ID, workspace, timezone, or date range is correct when it changes the result.

Workflow

  1. Identify the requested outcome and scope: account, workspace, entity IDs, date range, and whether the user wants a preview or a change.
  2. Read the relevant API contract before choosing endpoints. The contract links are listed below. The OpenAPI host may say localhost; use the production API host from Toggl's official documentation, not that placeholder.
  3. For an unfamiliar account or target, make read-only calls first to discover valid workspace and entity IDs. Never infer IDs from names or select the first match without confirming ambiguity.
  4. Present a concise plan for consequential or multi-record changes, including which records and fields will change. Get confirmation before creating, updating, deleting, starting, or stopping records unless the user explicitly requested that exact operation and target.
  5. Execute the smallest set of calls. For repeated or structured calls, use scripts/toggl_api.py; do not construct shell command strings from user data.
  6. Verify the result with a read-back call where available. Report changed IDs and any partial failures; do not claim success based only on a successful HTTP response when the contract indicates asynchronous or delayed behavior.

Authentication and safety

Installs
2
First Seen
Oct 29, 2026