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.
npx skills add https://github.com/jdrhyne/agent-skills --skill todo-tracker
Maintain a persistent TODO.md scratch pad in the workspace.
TODO.md in workspace root (e.g., /Users/nuthome/nuri-bot/TODO.md)
When user asks: "what's on the TODO?", "show TODO", "pending tasks?"
cat TODO.md
Then summarize the items by priority.
When user says: "add X to TODO", "TODO: X", "remember to X"
bash skills/todo-tracker/scripts/todo.sh add "<priority>" "<item>"
Priorities: high, medium, low (default: medium)
Examples:
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"
When user says: "mark X done", "completed X", "finished X"
bash skills/todo-tracker/scripts/todo.sh done "<item-pattern>"
Matches partial text. Moves item to ✅ Done section with date.
When user says: "remove X from TODO", "delete X from TODO"
bash skills/todo-tracker/scripts/todo.sh remove "<item-pattern>"
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
On heartbeat, check TODO.md:
Example heartbeat check:
bash skills/todo-tracker/scripts/todo.sh summary
# 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)
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)
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.
Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.
Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
Take jdrhyne/todo-tracker from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.