Imported from withoneai/one-agent-plugin (platforms/one-clockify/skills/clockify/SKILL.md). Install upstream with npx skills add withoneai/one-agent-plugin --skill clockify. Copyright stays with the author.

name: clockify description: Clockify is a time tracking and timesheet platform that enables teams and businesses to record work hours, manage projects, track billable time, and analyze productivity through web, mobile, and API-based integrations for reporting, payroll, and workflow automation. Read and write Clockify data through One: timeentries, workspaces, invoices, approvalrequests, webhooks, timeoffrequests and more, 155 actions with real parameter documentation. Use whenever the user asks to look something up in Clockify, create or update a record there, or build code against the Clockify API. license: One-Knowledge-1.0 (https://www.withone.ai/licenses/knowledge) metadata: author: one-systems attribution: Integration knowledge by One (withone.ai) platform: clockify generated-from: one-knowledge-base

Clockify through One

Clockify is a time tracking and timesheet platform that enables teams and businesses to record work hours, manage projects, track billable time, and analyze productivity through web, mobile, and API-based integrations for reporting, payroll, and workflow automation.

One exposes Clockify through four MCP tools. The table below carries real action ids from One's knowledge base, so for a common operation you can skip search and go straight to reading the action's parameters.

How to run an action

1. Find the action in the table below, or call search_one_platform_actions with platform clockify if it is not listed.
2. Call get_one_action_knowledge with the action id. Do this every time, including for actions in this table. The table gives you the id, not the parameters.
3. Call execute_one_action with parameters copied from that knowledge.

Never guess a parameter name, a body field, or an enum value. The knowledge has the real schema, and a guessed field is either a 400 or a silent write of the wrong thing.

Before you start

Call list_one_integrations once and confirm Clockify is connected. If it is missing, the user has not connected it: say so and point them at https://app.withone.ai rather than reaching for raw HTTP.

Each connection carries an access field. If it reports {"policy": "methods", "methods": ["GET"]} the agent is read-only here, so plan a read-only answer instead of attempting a write that will be refused.

Before a write

Creates, updates, deletes and sends land on a real Clockify account and cannot be recalled. State the action and the specific target in one line before the first write in a task, and let the user stop you. Reads need no confirmation.

Actions

TimeEntries

Workspaces

Invoices

ApprovalRequests

Webhooks

TimeOffRequests

Holidays

Expenses

WorkspaceUsers

Tags

Clients

WorkspaceCustomFields

Users

RecurringAssignments

Tasks

Balances

Projects

ProjectCustomFields

ExpenseCategories

ProjectAssignmentTotals

MemberProfile

UpdatedEntities

TimeOffPolicies

UserGroups

InvoicePayments

CustomFields

DeletedEntities

WorkspaceWebhooks

UserRoles

User

WorkspaceAssignmentSeries

WorkspaceUserTotals

ProjectTotals

This lists 90 of 155 actions. For anything not here, call search_one_platform_actions with platform clockify. The full catalog is at https://www.withone.ai/knowledge/clockify.

When a call fails

The error comes from Clockify, not from One. A 400 or 422 means your parameters do not match the schema, so re-read the knowledge and fix the field. A 401 or 403 means the connection needs re-authorizing, which no retry will fix. A 404 means the id is not on this account. A 429 means slow down. Never retry a write more than once: the first attempt may have landed.

Full catalog: https://www.withone.ai/knowledge/clockify

Integration knowledge by One (withone.ai), licensed under One-Knowledge-1.0. Attribution must be preserved in derivative works.