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.
Best use case
task-tracker is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using task-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/task-tracker/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How task-tracker Compares
| Feature / Agent | task-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?
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.
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
<div align="center">





**Personal task management with daily standups and weekly reviews**
[Homepage](https://github.com/kesslerio/task-tracker-clawdbot-skill) • [Trigger Patterns](#what-this-skill-does) • [Commands](#commands-reference)
</div>
---
# 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:**
```markdown
# 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
```bash
python3 ~/clawd/skills/task-tracker/scripts/tasks.py list
```
### Daily Standup
```bash
python3 ~/clawd/skills/task-tracker/scripts/standup.py
```
### Weekly Review
```bash
python3 ~/clawd/skills/task-tracker/scripts/weekly_review.py
```
---
## Commands Reference
### List Tasks
```bash
# All tasks
tasks.py list
# Only high priority
tasks.py list --priority high
# Only blocked
tasks.py list --status blocked
# Due today or this week
tasks.py list --due today
tasks.py list --due this-week
```
### Add Task
```bash
# 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
```bash
tasks.py done "proposal" # Fuzzy match - finds "Draft project proposal"
```
### Show Blockers
```bash
tasks.py blockers # All blocking tasks
tasks.py blockers --person sarah # Only blocking Sarah
```
### Extract from Meeting Notes
```bash
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
- **Telegram Journaling group:** Standup/review summaries posted automatically
- **Obsidian:** Daily standups logged to `01-Daily/YYYY-MM-DD.md`
- **MEMORY.md:** Patterns and recurring blockers promoted during weekly reviews
- **Cron:** Automated standups and reviews
---
## Troubleshooting
**"Tasks file not found"**
```bash
# Create from template
python3 scripts/init.py
```
**Tasks not showing up**
- Check TASKS.md exists at `~/clawd/memory/work/TASKS.md`
- Verify task format (checkboxes `- [ ]`, headers `## 🔴`)
- Run `tasks.py list` to debug
**Date parsing issues**
- Due dates support: `ASAP`, `YYYY-MM-DD`, `Before Mar 15`, `Before product launch`
- `check_due_date()` handles common formats
---
## Files
| 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 |Related Skills
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.
task-monitor
Real-time web dashboard for OpenClaw sessions and background tasks. Mobile-responsive with auto-refresh.
task-runner
Manage tasks and projects across sessions with persistent task tracking.
plant-tracker
Personal plant and garden management for gardeners.
pest-disease-tracker
Track garden pests and diseases with treatments.
farm-task-manager
*Daily, weekly, and seasonal farm chore management with task scheduling and priorities.*.
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.