deepwork-tracker
Track deep work sessions locally (start/stop/status) and generate a GitHub-contribution-graph style minutes-per-day heatmap for sharing (e.g., via Telegram). Use when the user says things like “start deep work”, “stop deep work”, “am I in a session?”, “show my deep work graph”, or asks to review deep work history.
Best use case
deepwork-tracker is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Track deep work sessions locally (start/stop/status) and generate a GitHub-contribution-graph style minutes-per-day heatmap for sharing (e.g., via Telegram). Use when the user says things like “start deep work”, “stop deep work”, “am I in a session?”, “show my deep work graph”, or asks to review deep work history.
Teams using deepwork-tracker should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/deepwork-tracker/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How deepwork-tracker Compares
| Feature / Agent | deepwork-tracker | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Track deep work sessions locally (start/stop/status) and generate a GitHub-contribution-graph style minutes-per-day heatmap for sharing (e.g., via Telegram). Use when the user says things like “start deep work”, “stop deep work”, “am I in a session?”, “show my deep work graph”, or asks to review deep work history.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Deepwork Tracker Use the local deepwork app (SQLite-backed) at `~/clawd/deepwork/deepwork.js`. ## Bootstrap (if the script is missing) If `~/clawd/deepwork/deepwork.js` does not exist, bootstrap it from the public repo: ```bash mkdir -p ~/clawd cd ~/clawd # Clone if missing [ -d ~/clawd/deepwork-tracker/.git ] || git clone https://github.com/adunne09/deepwork-tracker.git ~/clawd/deepwork-tracker # Ensure expected runtime path exists mkdir -p ~/clawd/deepwork cp -f ~/clawd/deepwork-tracker/app/deepwork.js ~/clawd/deepwork/deepwork.js chmod +x ~/clawd/deepwork/deepwork.js ``` (Do not fail the user request if clone/copy fails—still attempt other steps and report what’s missing.) ## Commands Run via exec: - Start a session (also starts a macOS Clock timer; default target 60m): - `~/clawd/deepwork/deepwork.js start --target-min 60` - Stop a session: - `~/clawd/deepwork/deepwork.js stop` - Check status: - `~/clawd/deepwork/deepwork.js status` - Generate a report: - Last 7 days (default): `~/clawd/deepwork/deepwork.js report --days 7 --format text` - Telegram-ready last 7 days: `~/clawd/deepwork/deepwork.js report --days 7 --format telegram` - Heatmap (optional): `~/clawd/deepwork/deepwork.js report --mode heatmap --weeks 52 --format telegram` ## Chat workflows ### Start deep work 1) Run `~/clawd/deepwork/deepwork.js start --target-min 60` (or another target if the user specifies it). 2) This should also start a macOS Clock timer for the target duration (best-effort; may require Accessibility permissions). 3) Reply with the confirmation line. ### Stop deep work 1) Run `~/clawd/deepwork/deepwork.js stop`. 2) Reply with duration. ### Show deep work graph 1) Run `~/clawd/deepwork/deepwork.js report --days 7 --format telegram`. 2) **Always send** the output to Alex on Telegram (id `8551040296`) using the `message` tool with a Markdown monospace code block. 3) Optionally acknowledge in the current chat that it was sent. If the user wants different ranges, support `--days 7|14|30|60`. (Heatmap is still available via `--mode heatmap --weeks ...` when explicitly requested.)
Related Skills
task-tracker
Personal task management with daily standups and weekly reviews. Use when: (1) User says 'daily standup' or asks what's on their plate, (2) User says 'weekly review' or asks about last week's progress, (3) User wants to add/update/complete tasks, (4) User asks about blockers or deadlines, (5) User shares meeting notes and wants tasks extracted, (6) User asks 'what's due this week' or similar.
yandex-tracker
Work with Yandex Tracker (issues, queues, comments, attachments, links, search, bulk operations) via Python.
invoice-tracker-pro
Complete freelance billing workflow — generate professional invoices, track payment status, send automated.
saas-revenue-tracker
Track SAAS revenue, MRR growth, customer metrics, and profitability.
research-tracker
Manage autonomous AI research agents with SQLite-based state tracking. Use when spawning long-running research sub-agents, tracking multi-step investigations, coordinating agent handoffs, or monitoring background work. Triggers on: research projects, sub-agent coordination, autonomous investigation, progress tracking, agent oversight.
plant-tracker
Personal plant and garden management for gardeners.
pest-disease-tracker
Track garden pests and diseases with treatments.
compost-tracker
Track compost piles, monitor temperature, record turns, and manage your organic waste decomposition.
package-tracker
Track packages and shipments via the 17track API.
release-tracker
Track GitHub repository releases and generate prioritized summaries.
pregnancy-tracker
Track pregnancy journey with weekly updates, symptom logging, and milestone countdowns
habit-tracker
Build habits with streaks, reminders, and progress visualization