Clockify Automation
by ComposioHQClockify Automation helps Claude Code users automate Clockify time tracking with Rube MCP, including creating time entries, querying history, managing workspace context, and auditing team activity.
This skill scores 68/100, which means it is acceptable for listing but should be presented as a lightweight MCP skill rather than a fully self-contained automation package. Directory users get enough evidence to understand when to trigger it—Clockify time-entry, workspace, and user/time-audit automation through Rube—and enough parameter guidance to improve on a generic prompt, but adoption still depends on external toolkit docs and prior configuration of the Rube MCP server.
- Valid skill frontmatter declares the required MCP dependency (`rube`) and a clear Clockify automation purpose.
- SKILL.md includes setup steps and links to the Composio Clockify toolkit docs for tool-level details.
- Core workflow examples name concrete tools such as `CLOCKIFY_CREATE_TIME_ENTRY` and list key parameters like `workspaceId`, `start`, `end`, `projectId`, `taskId`, tags, billable status, and custom fields.
- No install command or companion README/support files are present; setup is limited to adding the Rube MCP server and authenticating Clockify.
- Repository evidence shows low practical/workflow signal counts and no scripts or references beyond the SKILL.md, so users may need Clockify/Composio familiarity for IDs, permissions, and edge cases.
Overview of Clockify Automation skill
What Clockify Automation does
Clockify Automation is a Claude Code skill for controlling Clockify time tracking through natural language, using the Rube MCP server and Composio Clockify toolkit. It helps you create time entries, query historical entries, manage workspace context, inspect users, and audit team activity without switching from your terminal to the Clockify UI.
Best-fit users and jobs
This skill fits developers, consultants, agencies, team leads, and operations users who already use Clockify and want faster time-entry workflows. The real job is not just “log time”; it is turning messy work context into complete Clockify API actions with the right workspaceId, project, task, dates, billable flag, tags, and descriptions.
What makes it different from a generic prompt
A normal prompt can draft a timesheet note, but it cannot reliably execute Clockify actions. The Clockify Automation skill is useful because it maps user requests to specific toolkit actions such as CLOCKIFY_CREATE_TIME_ENTRY and expects Clockify-native identifiers and ISO 8601 time values. That structure reduces ambiguity when you need repeatable Workflow Automation instead of advice.
Main adoption considerations
You need a Clockify account, Claude Code, and access to the Rube MCP server at https://rube.app/mcp. The skill has a single visible source file, SKILL.md, so installation is lightweight, but users must supply accurate workspace, project, task, tag, and user IDs. If your team relies heavily on custom Clockify conventions, you should document those before expecting high-quality automation.
How to Use Clockify Automation skill
Clockify Automation install context
To use the Clockify Automation skill, install or enable it from ComposioHQ/awesome-claude-skills at composio-skills/clockify-automation, then configure Claude Code with the Rube MCP server URL: https://rube.app/mcp. During first use, authenticate your Clockify account through the connection link. The upstream skill does not include helper scripts or extra reference folders, so read SKILL.md first and verify the Composio toolkit docs at https://composio.dev/toolkits/clockify if you need tool-level details.
Inputs the skill needs before acting
Good Clockify Automation usage depends on precise Clockify context. Prepare:
workspaceIdfor the target workspaceprojectIdandtaskIdwhen the entry must be categorized- Start and end times in ISO 8601, including timezone
- Description text that matches your reporting standards
tagIds,billable, and custom field values when required- User or date filters when querying entries or auditing team work
A weak request is: “Log my API work this morning.”
A stronger request is: “Use Clockify Automation to create a billable entry in workspace 64a687e3, project 64a687e2, from 2026-02-11T09:00:00Z to 2026-02-11T11:00:00Z, description API development for invoice endpoint, with tag IDs ["backend","client-work"] if valid.”
Practical Clockify Automation usage workflow
Start by asking the skill to identify the workspace and available project context if you do not already know the IDs. Then create or query entries in small batches before automating a whole timesheet. For daily use, a reliable workflow is:
- Query existing entries for the target date to avoid duplicates.
- Create missing entries with exact start/end timestamps.
- Confirm billable status, project, task, and tags.
- Ask for a summary grouped by project or client.
- Correct any mismatched IDs before repeating the pattern.
This prevents the most common failure: logging plausible entries into the wrong workspace or project.
Prompt patterns that improve output
Use action-oriented prompts that name the desired Clockify operation. For example:
- “Create a running timer for workspace
...starting now with descriptionCode review.” - “Find all time entries for user
...in workspace...between2026-02-01and2026-02-07.” - “Audit yesterday’s team entries and flag missing descriptions, non-billable entries on billable projects, and entries longer than 8 hours.”
These prompts work better than broad requests because they include the operation, scope, dates, and validation criteria.
Clockify Automation skill FAQ
Is Clockify Automation good for beginners?
Yes, if you already understand your Clockify workspace structure. Beginners can use it to log and search time entries, but they may need help finding workspace, project, task, and tag IDs. The skill is not a replacement for learning how your organization organizes Clockify data.
When should I not use this skill?
Do not use Clockify Automation when you only need a written timesheet summary, when you cannot authenticate Clockify through Rube MCP, or when your request is too vague to safely modify time records. For sensitive billing workflows, ask the skill to query and preview entries before creating or editing anything.
How is this different from Clockify’s web app?
Clockify’s web app is best for visual review and manual edits. The Clockify Automation skill is better for terminal-first workflows, repeatable natural-language actions, and quick audits across time entries. It is especially useful for Workflow Automation where you want Claude Code to handle structured Clockify operations while you stay in your development environment.
What should I read before installing?
Read composio-skills/clockify-automation/SKILL.md. It contains the setup flow, core workflows, example tool calls, and important parameters such as workspaceId, start, end, projectId, taskId, tagIds, billable, and customFieldValues. There are no extra local scripts or resources in the skill folder, so the source file is the main implementation guide.
How to Improve Clockify Automation skill
Improve Clockify Automation inputs
The fastest way to improve results is to maintain a small internal reference of your Clockify IDs: workspace, projects, tasks, tags, users, and custom fields. Include naming rules such as “client work must be billable” or “support entries require tag support.” Then paste the relevant subset into your prompt so the skill does not have to infer business logic.
Avoid common failure modes
Watch for timezone ambiguity, missing end times, duplicate entries, wrong workspace IDs, and inconsistent project naming. If a request affects billing, ask for a dry-run style plan first: “List the entries you intend to create, including IDs and timestamps, before calling the Clockify tool.” This adds a useful checkpoint without abandoning automation.
Iterate after the first output
After the first query or creation, refine with concrete corrections: “Change the description to include ticket API-482,” “mark only the client project entries as billable,” or “split the 4-hour entry into two 2-hour entries by task.” Iteration works best when you reference exact entry details returned by the skill instead of restating the whole goal.
Make it better for team workflows
For team use, standardize prompt templates for daily logging, weekly audits, and missing-entry checks. A strong Clockify Automation guide inside your repo can include approved project IDs, required tags, billing rules, and example prompts. That local context turns the skill from a convenient Clockify shortcut into a dependable team automation layer.