Task Tracker
by @kesslerio
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.
clawhub install task-trackerπ About This Skill
name: task-tracker description: "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." homepage: https://github.com/kesslerio/task-tracker-clawdbot-skill metadata: {"clawdbot":{"emoji":"π","requires":{"files":["~/clawd/memory/work/TASKS.md"]},"install":[{"id":"init","kind":"script","script":"python3 scripts/init.py","label":"Initialize TASKS.md from template"}]}}
!Task Tracker !Python !Status !Issues !Last Updated
Personal task management with daily standups and weekly reviews
Homepage β’ Trigger Patterns β’ Commands
Task Tracker
A personal task management skill for daily standups and weekly reviews. Tracks work tasks, surfaces priorities, and manages blockers.
What This Skill Does
1. Lists tasks - Shows what's on your plate, filtered by priority, status, or deadline 2. Daily standup - Shows today's #1 priority, blockers, and what was completed 3. Weekly review - Summarizes last week, archives done items, plans this week 4. Add tasks - Create new tasks with priority and due date 5. Complete tasks - Mark tasks as done 6. Extract from notes - Pull action items from meeting notes
File Structure
~/clawd/memory/work/
βββ TASKS.md # Active tasks (source of truth)
βββ ARCHIVE-2026-Q1.md # Completed tasks by quarter
βββ WORKFLOW.md # Workflow documentation
TASKS.md format:
# Work Tasksπ΄ High Priority (This Week)
[ ] Set up Apollo.io β Access for Lilla
- Due: ASAP
- Blocks: Lilla (podcast outreach)π‘ Medium Priority (This Week)
[ ] Review newsletter concept β Figma design
- Due: Before Feb 1β
Done
[x] Set up team calendar β Shared Google Calendar
Quick Start
View Your Tasks
python3 ~/clawd/skills/task-tracker/scripts/tasks.py list
Daily Standup
python3 ~/clawd/skills/task-tracker/scripts/standup.py
Weekly Review
python3 ~/clawd/skills/task-tracker/scripts/weekly_review.py
Commands Reference
List Tasks
# All tasks
tasks.py listOnly high priority
tasks.py list --priority highOnly blocked
tasks.py list --status blockedDue today or this week
tasks.py list --due today
tasks.py list --due this-week
Add Task
# Simple
tasks.py add "Draft project proposal"With details
tasks.py add "Draft project proposal" \
--priority high \
--due "Before Mar 15" \
--blocks "Sarah (client review)"
Complete Task
tasks.py done "proposal" # Fuzzy match - finds "Draft project proposal"
Show Blockers
tasks.py blockers # All blocking tasks
tasks.py blockers --person sarah # Only blocking Sarah
Extract from Meeting Notes
extract_tasks.py --from-text "Meeting: discuss Q1 planning, Sarah to own budget review"
Outputs: tasks.py add "Discuss Q1 planning" --priority medium
tasks.py add "Sarah to own budget review" --owner sarah
Priority Levels
| Icon | Meaning | When to Use | |------|---------|-------------| | π΄ High | Critical, blocking, deadline-driven | Revenue impact, blocking others | | π‘ Medium | Important but not urgent | Reviews, feedback, planning | | π’ Low | Monitoring, delegated | Waiting on others, backlog |
Status Workflow
Todo β In Progress β Done
β³ Blocked (waiting on external)
β³ Waiting (delegated, monitoring)
Automation (Cron)
| Job | When | What | |-----|------|------| | Daily Standup | Weekdays 8:30 AM | Posts to Telegram Journaling group | | Weekly Review | Mondays 9:00 AM | Posts summary, archives done items |
Natural Language Triggers
| You Say | Skill Does | |---------|-----------| | "daily standup" | Runs standup.py, posts to Journaling | | "weekly review" | Runs weekly_review.py, posts summary | | "what's on my plate?" | Lists all tasks | | "what's blocking Lilla?" | Shows tasks blocking Lilla | | "mark IMCAS done" | Completes matching task | | "what's due this week?" | Lists tasks due this week | | "add task: X" | Adds task X to TASKS.md | | "extract tasks from: [notes]" | Parses notes, outputs add commands |
Examples
Morning check-in:
$ python3 scripts/standup.pyπ Daily Standup β Tuesday, January 21
π― #1 Priority: Complete project proposal draft
β³ Blocking: Sarah (client review)
β° Due Today:
β’ Complete project proposal draft
β’ Schedule team sync
π΄ High Priority:
β’ Review Q1 budget (due: Before Mar 15)
β’ Draft blog post (due: ASAP)
β
Recently Completed:
β’ Set up shared calendar
β’ Update team documentation
Adding a task:
$ python3 scripts/tasks.py add "Draft blog post" --priority high --due ASAPβ
Added task: Draft blog post
Extracting from meeting notes:
$ python3 scripts/extract_tasks.py --from-text "Meeting: Sarah needs budget review, create project timeline"Extracted 2 task(s) from meeting notes
Run these commands to add them:
tasks.py add "Budget review for Sarah" --priority high
tasks.py add "Create project timeline" --priority medium
Integration Points
01-Daily/YYYY-MM-DD.mdTroubleshooting
"Tasks file not found"
# Create from template
python3 scripts/init.py
Tasks not showing up
~/clawd/memory/work/TASKS.md- [ ], headers ## π΄)tasks.py list to debugDate parsing issues
ASAP, YYYY-MM-DD, Before Mar 15, Before product launchcheck_due_date() handles common formatsFiles
| File | Purpose |
|------|---------|
| scripts/tasks.py | Main CLI - list, add, done, blockers, archive |
| scripts/standup.py | Daily standup generator |
| scripts/weekly_review.py | Weekly review generator |
| scripts/extract_tasks.py | Extract tasks from meeting notes |
| scripts/utils.py | Shared utilities (DRY) |
| scripts/init.py | Initialize new TASKS.md from template |
| references/task-format.md | Task format specification |
| assets/templates/TASKS.md | Template for new task files |
π‘ Examples
Morning check-in:
$ python3 scripts/standup.pyπ Daily Standup β Tuesday, January 21
π― #1 Priority: Complete project proposal draft
β³ Blocking: Sarah (client review)
β° Due Today:
β’ Complete project proposal draft
β’ Schedule team sync
π΄ High Priority:
β’ Review Q1 budget (due: Before Mar 15)
β’ Draft blog post (due: ASAP)
β
Recently Completed:
β’ Set up shared calendar
β’ Update team documentation
Adding a task:
$ python3 scripts/tasks.py add "Draft blog post" --priority high --due ASAPβ
Added task: Draft blog post
Extracting from meeting notes:
$ python3 scripts/extract_tasks.py --from-text "Meeting: Sarah needs budget review, create project timeline"Extracted 2 task(s) from meeting notes
Run these commands to add them:
tasks.py add "Budget review for Sarah" --priority high
tasks.py add "Create project timeline" --priority medium
π Tips & Best Practices
"Tasks file not found"
# Create from template
python3 scripts/init.py
Tasks not showing up
~/clawd/memory/work/TASKS.md- [ ], headers ## π΄)tasks.py list to debugDate parsing issues
ASAP, YYYY-MM-DD, Before Mar 15, Before product launchcheck_due_date() handles common formats