deepwork-tracker
/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.
- Author
- aAAaqwq ↗
- Repository
- AGI-Super-Team ↗
- Licence
- MIT
- Last repository change
- 20.10.2026
Assessment and security
- Files in this package
- 3
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 1
No signals detected. Repository changed on 20.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
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.
Triggers from the description
Original author description
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.
How it works
- Bootstrap (if the script is missing)
- Commands
- Chat workflows
SKILL.md preview
--- name: deepwork-tracker description: 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. --- # 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.)
Files in this package (3)
- SKILL.md 2 KB
- _meta.json 1 KB
- .clawhub/origin.json 1 KB
Versions
The database has no other skills named deepwork-tracker.
Identical content appears in 5 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 383b82ad007d (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 95obsidian-tracker-track-stop
Stop tracking and save session to Obsidian. Use when the user invokes /track-stop. - 100deep-work
Use when someone wants to plan a deep work day, time-block their calendar or task list, budget or cut shallow work, protect focus hours, track deep-work sessions and streaks, run an end-of-day shutdown ritual, or says "/deep-work" or "/time-block". Classifies tasks deep vs… - 95obsidian-tracker-track-start
Start tracking current session for Obsidian. Use when the user invokes /track-start. - 100deep-history
Cross-session deep-work history — completed sessions, TDD compliance rates, model usage, aggregate trend indicators. Triggers on `/deep-history`, `/deep-status --history`, \"session history\", \"deep-work history\", \"세션 이력\", \"이전 세션\", \"TDD 준수율 트렌드\". Sub-page of the deep-status hub. - 100deep-work-planner
Designs a daily schedule that protects deep work - classifies tasks as deep or shallow, places 2-4 focus blocks of 60-120 minutes at peak energy hours, batches shallow work into fixed windows, and defines each session with a goal, definition of done, distraction plan, and first… - 100deep-work
运用《深度工作》(Cal Newport) 的四准则框架,指导用户设计注意力管理与深度工作系统。适用于用户想提升专注产出、日程被浮浅事务淹没、设计个人深度工作习惯(哲学选型/时间块/固定日程)、评估是否该戒断某网络工具、以及诊断"忙一天却没什么成果"时使用。