How do I install the Clockify Uninit skill?

Run npx skillmds@latest add dustinestes/clockify-uninit 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 Uninit 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 Uninit?

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 Uninit free to use?

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

Who published Clockify Uninit?

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

Clockify Uninit by dustinestes — Agent Skill

Name: Clockify Uninit
Author: dustinestes

Clockify Uninit

Remove Clockify integration artifacts from a consumer repo: .clockify/, clockify rule, Clockify-owned hooks, and the managed gitignore stanza. Use when uninstalling repo Clockify standards. To pause and keep settings, use clockify-automate-disable; to reset automate yaml and keep config, use clockify-unautomate. Does not uninstall the Clockify Agent Plugin unless the user asks.

dustinestes c65984d 3.4 KB Updated Sep 17, 2026

File contents

Clockify uninit

Full local teardown of Clockify-owned files in a consumer repo. Confirm with the user before deleting.

If they only want to pause agent-mediated timers and keep forge/platform settings, stop and run clockify-automate-disable instead.

If they want to stop agent mode and reset automate yaml toward init defaults (keep .clockify/config.yml), stop and run clockify-unautomate instead.

Confirm

Inventory with tools if needed, then repeat the result in a normal chat message the user can read without opening tool output. Use a short markdown list of paths that exist (and optionally “not found” for expected paths). Tool snippets / terminals are not the inventory.
That chat list is the confirm surface: unautomate paths plus .clockify/, the remaining gitignore stanza, and .gitignore itself if removing the stanza would leave the file empty. Note that the Clockify Agent Plugin stays installed unless they ask otherwise.
If .clockify/.managed-by-init is missing, still include those well-known paths in the chat inventory (user may have edited by hand).
Then AskQuestion with only a short confirm, e.g. “Remove Clockify files from this repo?” — do not put the inventory in the question box, and do not skip the chat list.
Do not uninstall the Clockify Agent Plugin unless the user explicitly asks.

Removals

Perform clockify-unautomate first (rule + Clockify-owned hooks + rule gitignore line), then:

Delete .clockify/ entirely (config, marker, self-ignore, any extras).
Remove the remaining managed gitignore stanza when present (idempotent match on either comment header):
```
# Clockify Agent Plugin — personal time-tracking (delete this block to share with the team)
.clockify/
```
Also match the older header # Clockify MCP — personal time-tracking if a repo was inited before the rename.

If the stanza still lists the rule path or .cursor/hooks/clockify-runaway.sh (unautomate not run yet), remove those lines together.
After stanza removal: if .gitignore is empty or whitespace-only, delete the file (same idea as deleting empty hooks.json in unautomate). If any other ignore rules remain, keep the file. Never delete a non-empty .gitignore. No need to know whether init created the file — emptiness after our stanza is gone is enough.

Do not

Wipe unrelated Cursor hooks or rules
Delete a non-empty .gitignore (empty / whitespace-only after stanza removal is OK — see above)
Uninstall Directory / local plugin or clear CLOCKIFY_API_KEY unless asked
Invent paths outside the well-known set above
Treat tool output as the user-visible inventory (always restate paths in chat before AskQuestion)

After

Summarize what was removed. The Clockify Agent Plugin may still be available at the user/plugin level. Repo yaml is gone until they run clockify-init again.

---name: clockify-uninitdescription: Remove Clockify integration artifacts from a consumer repo: .clockify/, clockify rule, Clockify-owned hooks, and the managed gitignore stanza. Use when uninstalling repo Clockify standards. To pause and keep settings, use clockify-automate-disable; to reset automate yaml and keep config, use clockify-unautomate. Does not uninstall the Clockify Agent Plugin unless the user asks.---# Clockify uninitFull local teardown of Clockify-owned files in a **consumer** repo. Confirm with the user before deleting.If they only want to **pause** agent-mediated timers and **keep** forge/platform settings, stop and run [`clockify-automate-disable`](../clockify-automate-disable/SKILL.md) instead.If they want to stop agent mode and **reset** automate yaml toward init defaults (keep `.clockify/config.yml`), stop and run [`clockify-unautomate`](../clockify-unautomate/SKILL.md) instead.## Confirm1. Inventory with tools if needed, then **repeat the result in a normal chat message** the user can read without opening tool output. Use a short markdown list of **paths that exist** (and optionally “not found” for expected paths). Tool snippets / terminals are not the inventory.2. That chat list is the confirm surface: unautomate paths plus `.clockify/`, the remaining gitignore stanza, and `.gitignore` itself if removing the stanza would leave the file empty. Note that the Clockify Agent Plugin stays installed unless they ask otherwise.3. If `.clockify/.managed-by-init` is missing, still include those well-known paths in the chat inventory (user may have edited by hand).4. Then AskQuestion with **only** a short confirm, e.g. “Remove Clockify files from this repo?” — do **not** put the inventory in the question box, and do **not** skip the chat list.5. Do **not** uninstall the Clockify Agent Plugin unless the user explicitly asks.## RemovalsPerform [`clockify-unautomate`](../clockify-unautomate/SKILL.md) first (rule + Clockify-owned hooks + rule gitignore line), then:1. Delete `.clockify/` entirely (config, marker, self-ignore, any extras).2. Remove the remaining managed gitignore stanza when present (idempotent match on either comment header): ```gitignore # Clockify Agent Plugin — personal time-tracking (delete this block to share with the team) .clockify/ ``` Also match the older header `# Clockify MCP — personal time-tracking` if a repo was inited before the rename. If the stanza still lists the rule path or `.cursor/hooks/clockify-runaway.sh` (unautomate not run yet), remove those lines together.3. After stanza removal: if `.gitignore` is empty or whitespace-only, delete the file (same idea as deleting empty `hooks.json` in unautomate). If any other ignore rules remain, keep the file. Never delete a non-empty `.gitignore`. No need to know whether init created the file — emptiness after our stanza is gone is enough.## Do not- Wipe unrelated Cursor hooks or rules- Delete a non-empty `.gitignore` (empty / whitespace-only after stanza removal is OK — see above)- Uninstall Directory / local plugin or clear `CLOCKIFY_API_KEY` unless asked- Invent paths outside the well-known set above- Treat tool output as the user-visible inventory (always restate paths in chat before AskQuestion)## AfterSummarize what was removed. The Clockify Agent Plugin may still be available at the user/plugin level. Repo yaml is gone until they run `clockify-init` again.

Frequently asked questions