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.

Security Scan

The skill's claimed behavior (local task tracking and standups) mostly matches the files and commands present, but there are inconsistencies and missing declarations (notably Telegram/network integration and an install script) that warrant review before installation.

Purpose & Capability

Name/description match the code and CLI commands: scripts for listing, adding, completing, extracting, standup and weekly review exist and operate on a TASKS.md under ~/clawd/memory/work which is declared in the SKILL.md metadata. That is coherent for a personal task-tracker.

Instruction Scope

SKILL.md instructs running local Python scripts that will read/write ~/clawd/memory/work/TASKS.md and archive files. It also describes automatic posting to a Telegram journaling group and extraction from free-text meeting notes (which produces shell commands). The skill's runtime instructions allow executing generated shell commands and performing file writes; parsing arbitrary notes into commands can create risks (e.g., accidental command injection) if outputs are executed without review.

Install Mechanism

Registry metadata initially listed 'No install spec', but SKILL.md metadata contains an install entry that runs 'python3 scripts/init.py'. That is an on-disk install action (script execution) and should be reviewed; installer scripts can modify files. No external downloads are present, which lowers remote-code risk, but the presence of an install script that will be executed automatically is under-declared in the registry summary and is a mismatch to note.

Credentials

Registry lists no required environment variables, yet the docs/Automation claim posting to Telegram (and a scripts/telegram-commands.sh file exists). There is no declared TELEGRAM_TOKEN or similar credential in requires.env. If the skill posts to Telegram or other network endpoints, credentials and network destinations should be explicitly declared; absence is an incoherence and could hide required sensitive configuration or unexpected network behavior.

Persistence & Privilege

The skill does not set always:true and does not disable model invocation, so the model could invoke the skill autonomously. For a task manager that reads/writes local memory files, this is moderately privileged but not unusual. Because the skill can run local scripts and may post externally, consider disabling autonomous invocation or requiring explicit user confirmation for actions that modify files or send external messages.

What to consider before installing

This skill largely looks like a local task manager, but a few mismatches deserve attention before installing: - Review the actual script contents (scripts/*.py and scripts/telegram-commands.sh) before running the install or init script. The SKILL.md will run python3 scripts/init.py — inspect that script to see what files it creates or modifies. - Check for network calls in the scripts (HTTP requests, curl, or use of telegram APIs). If the skill is going to post to Telegram, it should declare the TELEGRAM_TOKEN or similar credential; absence of such an env var in the registry is suspicious. Don't provide secrets until you confirm where/how they're used. - Be cautious with the extract_tasks flow: it parses free text and emits shell commands like tasks.py add ... — ensure those outputs are never executed automatically on untrusted input to avoid injection. Prefer manual review of extracted commands or add sanitization. - Because the model can invoke the skill by default, consider setting disableModelInvocation or requiring explicit user triggers if you want to avoid autonomous modifications to your TASKS.md. If you want higher confidence, provide the contents of the scripts (init.py, tasks.py, extract_tasks.py, telegram-commands.sh) so they can be inspected for network destinations, shell execution, credential use, or writes to paths outside ~/clawd/memory/work.

<div align="center">

Personal task management with daily standups and weekly reviews

Homepage • Trigger Patterns • Commands

</div>

---

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 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

# 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

• 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"

# 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