2.5k
GitHub Stars
8
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill openclaw/skills --skill claw-todolist- _meta.json302 B
- display_config.json123 B
- import_tasks.txt1.2 KB
- index.js16.0 KB
- package.json174 B
- SKILL.md1.3 KB
- task_state.json234 B
- todo-rules-v3.2.md1.5 KB
Overview
This skill is a structured, conversational task manager implementing the Todo List Management Protocol V3.2. It organizes tasks by Priority Groups, Weight (⭐), and due dates, and confines all persistence to its own skill directory for deterministic storage. The interface supports concise aliases and a REVIEW command for weekly structural analysis. It is optimized for focused GTD and Eisenhower-style workflows.
How this skill works
You interact with the skill through short commands and aliases: a (ADD), x (DONE), ls (SHOW), e (EDIT), and REVIEW for structural audits. Tasks are stored locally within the skill folder using the V3.2 ruleset, and display output is a structured text list with Priority Group headers and Weight stars after task text. REVIEW runs automated checks against thresholds such as P1 Ratio, Overdue, Aging, and Strategic Neglect, and returns actionable findings to rebalance your task set.
When to use it
- When you need a lightweight, local task store with deterministic persistence.
- For weekly structuring and prioritization using GTD and Eisenhower principles (use REVIEW).
- When you want quick, keyboard-friendly commands and aliases for rapid task entry and completion.
- For teams or individuals who prefer text-based task lists with clear priority grouping and weight scoring.
Best practices
- Use the a alias for fast capture and include a Priority Group and due date when possible.
- Assign a Weight (⭐) to help triage tasks with similar priority levels.
- Run REVIEW weekly to detect overdue, aging, or strategically neglected items and act on its recommendations.
- Keep edits minimal and consistent; use e to correct priority, due date, or weight rather than re-adding tasks.
- Rely on ls to inspect the full structured view before making bulk changes.
Example use cases
- Quickly add a task: a Buy client report P2 due:2026-03-01 ⭐⭐
- Finish work items with x <task-id> to mark done and keep history confined to the skill folder.
- Use ls to produce a ready-to-read, shareable text list with Priority Group headers for status meetings.
- Run REVIEW each week to receive a short diagnostic: high P1 ratio, overdue items, and recommendations to rebalance priorities.
- Edit a task’s due date or weight with e when priorities shift mid-sprint.
FAQ
No. All state, rules, and display configurations are persisted only within the skill’s directory for deterministic local storage.
What does REVIEW do and how often should I run it?
REVIEW runs automated checks against thresholds like P1 Ratio, Overdue, Aging, and Strategic Neglect, and produces recommendations. Run it weekly or whenever your task load feels unbalanced.