How do I install the Clockify Enter Time skill?

Run npx skillmds@latest add dustinestes/clockify-enter-time in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Clockify Enter Time safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Clockify Enter Time?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Clockify Enter Time free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Clockify Enter Time?

dustinestes (@dustinestes) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Clockify Enter Time by dustinestes — Agent Skill

Name: Clockify Enter Time
Author: dustinestes

Clockify Enter Time

Create a completed Clockify time entry with an explicit start and end (Clockify Manual). Use when the user logs a range, backfills forgotten time, or does not want a running timer. Does not round. Infers a window only when times are omitted, and always confirms before writing.

dustinestes 7577170 2.2 KB Updated Sep 17, 2026

File contents

Clockify enter time

Manual method: clockify_create_time_entry with entry_method: manual. Typed times stay exact.

Config-aware behavior

If config_root is already known this session and still this repo, reuse it. Otherwise resolve once with git rev-parse --show-toplevel from the working directory (open tabs are not required; multi-root: focused path only as a tie-breaker; non-git: Cursor window folder). Re-resolve when the folder or focused root changes. Pass that string on Clockify MCP calls — do not run git before every tool.
clockify_get_config with config_root. Honor entry.manual.description, entry.manual.task, entry.manual.overlap. Do not apply rounding.
Never invent project/task ids.

Workflow

clockify_get_running_timer with config_root. If a timer is already running for this same work, do not double-count — point at clockify-stop-timer.
Resolve project (list/ensure). Resolve task from entry.manual.task.from / if_missing (same rules as start-timer: prompt, template, local_folder, fixed, or none).
Description: ask or use their text (entry.manual.description.from is always prompt; no issue templates).
Times given (e.g. 09:30–09:45): convert to ISO and create. Do not round.
Times omitted (forgot to track): infer start from cheap signals — git log / branch checkout, conversation timestamps, recent file edits. End defaults to now unless they give one. Show the inferred window and confirm. Never silently log hours.
clockify_create_time_entry with config_root and entry_method: manual. If overlap: true, show the clash. Retry with confirm_overlap: true only if they agree (or on_conflict is override). Override is how parallel completed streams can stack; do not treat that as the default.

Examples

User: "Log 9:30 to 10:15 on the login bug"

Config + running-timer check.
Create entry with those times, no rounding.

---name: clockify-enter-timedescription: Create a completed Clockify time entry with an explicit start and end (Clockify Manual). Use when the user logs a range, backfills forgotten time, or does not want a running timer. Does not round. Infers a window only when times are omitted, and always confirms before writing.---# Clockify enter time**Manual** method: `clockify_create_time_entry` with `entry_method: manual`. Typed times stay exact.## Config-aware behavior1. If `config_root` is already known this session and still this repo, reuse it. Otherwise resolve once with `git rev-parse --show-toplevel` from the working directory (open tabs are not required; multi-root: focused path only as a tie-breaker; non-git: Cursor window folder). Re-resolve when the folder or focused root changes. Pass that string on Clockify MCP calls — do not run git before every tool.2. `clockify_get_config` with `config_root`. Honor `entry.manual.description`, `entry.manual.task`, `entry.manual.overlap`. Do **not** apply rounding.3. Never invent project/task ids.## Workflow1. `clockify_get_running_timer` with `config_root`. If a timer is already running for this same work, do not double-count — point at `clockify-stop-timer`.2. Resolve project (list/ensure). Resolve task from `entry.manual.task.from` / `if_missing` (same rules as start-timer: `prompt`, `template`, `local_folder`, `fixed`, or `none`).3. Description: ask or use their text (`entry.manual.description.from` is always `prompt`; no issue templates).4. **Times given** (e.g. 09:30–09:45): convert to ISO and create. Do not round.5. **Times omitted** (forgot to track): infer start from cheap signals — git log / branch checkout, conversation timestamps, recent file edits. End defaults to now unless they give one. **Show the inferred window and confirm.** Never silently log hours.6. `clockify_create_time_entry` with `config_root` and `entry_method: manual`. If `overlap: true`, show the clash. Retry with `confirm_overlap: true` only if they agree (or `on_conflict` is `override`). Override is how parallel completed streams can stack; do not treat that as the default.## Examples**User:** "Log 9:30 to 10:15 on the login bug"1. Config + running-timer check.2. Create entry with those times, no rounding.

Frequently asked questions