home / skills / openclaw / skills / todo-tracker

todo-tracker skill

safe

This skill helps you manage a persistent TODO list across sessions, enabling quick add, view, complete, and remove actions.

npx playbooks add skill openclaw/skills --skill todo-tracker

Review the files below or copy the command above to add this skill to your agents.

Files (4)

SKILL.md

2.5 KB

---
name: todo-tracker
description: Persistent TODO scratch pad for tracking tasks across sessions. Use when user says "add to TODO", "what's on the TODO", "mark X done", "show TODO list", "remove from TODO", or asks about pending tasks. Also triggers on heartbeat to remind about stale items.
---

# TODO Tracker

Maintain a persistent TODO.md scratch pad in the workspace.

## File Location

`TODO.md` in workspace root (e.g., `/Users/nuthome/nuri-bot/TODO.md`)

## Commands

### View TODO
When user asks: "what's on the TODO?", "show TODO", "pending tasks?"
```bash
cat TODO.md
```
Then summarize the items by priority.

### Add Item
When user says: "add X to TODO", "TODO: X", "remember to X"
```bash
bash skills/todo-tracker/scripts/todo.sh add "<priority>" "<item>"
```
Priorities: `high`, `medium`, `low` (default: medium)

Examples:
```bash
bash skills/todo-tracker/scripts/todo.sh add high "Ingest low-code docs"
bash skills/todo-tracker/scripts/todo.sh add medium "Set up Zendesk escalation"
bash skills/todo-tracker/scripts/todo.sh add low "Add user memory feature"
```

### Mark Done
When user says: "mark X done", "completed X", "finished X"
```bash
bash skills/todo-tracker/scripts/todo.sh done "<item-pattern>"
```
Matches partial text. Moves item to ✅ Done section with date.

### Remove Item
When user says: "remove X from TODO", "delete X from TODO"
```bash
bash skills/todo-tracker/scripts/todo.sh remove "<item-pattern>"
```

### List by Priority
```bash
bash skills/todo-tracker/scripts/todo.sh list high
bash skills/todo-tracker/scripts/todo.sh list medium
bash skills/todo-tracker/scripts/todo.sh list low
```

## Heartbeat Integration

On heartbeat, check TODO.md:
1. Count high-priority items
2. Check for stale items (added >7 days ago)
3. If items exist, include brief summary in heartbeat response

Example heartbeat check:
```bash
bash skills/todo-tracker/scripts/todo.sh summary
```

## TODO.md Format

```markdown
# TODO - Nuri Scratch Pad

*Last updated: 2026-01-17*

## 🔴 High Priority
- [ ] Item one (added: 2026-01-17)
- [ ] Item two (added: 2026-01-15) ⚠️ STALE

## 🟡 Medium Priority
- [ ] Item three (added: 2026-01-17)

## 🟢 Nice to Have
- [ ] Item four (added: 2026-01-17)

## ✅ Done
- [x] Completed item (done: 2026-01-17)
```

## Response Format

When showing TODO:
```
📋 **TODO List** (3 items)

🔴 **High Priority** (1)
• Ingest low-code docs

🟡 **Medium Priority** (1)  
• Zendesk escalation from Discord

🟢 **Nice to Have** (1)
• User conversation memory

⚠️ 1 item is stale (>7 days old)
```

Overview

This skill provides a persistent TODO scratch pad stored in the workspace to track tasks across sessions. It lets you add, list, remove, and mark tasks done with priority tags and stale-item detection. The skill integrates with heartbeat checks to surface high-priority and stale items automatically. Use it to keep a simple, searchable task log that persists between interactions.

How this skill works

The skill maintains a TODO.md file in the workspace root and updates it when you add, complete, or remove items. Tasks are recorded with a priority (high, medium, low), an added date, and moved to a Done section when completed. The skill can list tasks by priority and summarize the full TODO with counts and stale-item warnings. A heartbeat check summarizes high-priority counts and flags items older than seven days.

When to use it

When you say "add to TODO" or "remember to X" to capture a new task.
When you ask "what's on the TODO" or "show TODO list" to review pending work.
When you say "mark X done" or "completed X" to record completion.
When you say "remove X from TODO" to delete incorrect or obsolete items.
During heartbeat or periodic checks to get reminders about high-priority or stale tasks.

Best practices

Specify a priority (high, medium, low) when adding tasks to keep the list actionable.
Use concise task descriptions and include context or links in the item text for clarity.
Mark items done rather than removing them to keep a historical record.
Review the TODO summary regularly and address stale items older than seven days.
Use listing by priority to focus on the most important tasks first.

Example use cases

Add a bug report or feature request quickly: "add high Ingest low-code docs to TODO".
Daily check-in: ask "what's on the TODO" to get prioritized tasks before standup.
Clean up after completion: "mark Zendesk escalation done" to move it to Done with a date.
Remove noise: "remove outdated config doc from TODO" when an item is no longer relevant.
Heartbeat reminder: receive a short summary of high-priority and stale items during periodic health checks.

FAQ

How are priorities handled?

When adding an item you can choose high, medium, or low; medium is the default if none is specified.

What makes an item stale?

An item is considered stale if it was added more than seven days ago; stale items are flagged in summaries and heartbeat responses.