Menu
TODO file format and operations
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Calendar operations with CalDAV
Git repository management, GitLab merge requests, and GitHub pull requests
Location tracking, place recognition, visit history, and calendar attendance
Persistent memory writes — USER.md (behavioral) and the knowledge graph (facts).
Accounting operations (ledger, invoicing, transactions, work log, investment portfolio) — runs in-process via the vendored money package
Send a push notification to the user's configured ntfy device(s). One-way (bot to phone), no reply channel.
| name | todos |
| triggers | ["todo","task","checklist","reminder","done","complete"] |
| description | TODO file format and operations |
TODO files are plain text with a simple format. Each line is a task:
- [ ] Uncompleted task
- [x] Completed task
- [ ] Task with @due(2025-01-30)
- [ ] Task with @priority(high)
When reading/updating TODO files, use standard file operations:
# Read the TODO file
cat {workspace}/path/to/TODO.txt
# Add a task
echo "- [ ] New task" >> {workspace}/path/to/TODO.txt
# Edit in place (changes save directly to your workspace)