🎁 Get the FREE AI Skills Starter Guide β€” Subscribe β†’
BytesAgainBytesAgain
πŸ¦€ ClawHub

Todo Boss

by @ukraecho

Capture and track tasks with owner and due date, mark done, list open or delegated tasks, and get daily reports via Telegram commands.

Versionv0.1.0
Downloads1,532
TERMINAL
clawhub install todo-boss

πŸ“– About This Skill

todo-boss

Purpose

Task capture + delegation tracking + daily remaining-work report for Telegram. NO web browsing, NO web search, NO external lookups.

Data store

Append-only log: ~/.openclaw/workspace/data/todo/tasks.jsonl Derived state cache (optional): ~/.openclaw/workspace/data/todo/state.json

Commands (Telegram)

  • /todo : create a task draft from free text
  • /todo_done : mark done
  • /todo_list : list open tasks (grouped by owner, then due date)
  • /todo_delegated : list tasks I assigned to others that are still open (include history)
  • /todo_report : daily report (same as list, but concise)
  • Extraction rules (very important)

    When user sends /todo : 1) Extract: title, owner, due_date (YYYY-MM-DD or natural language), priority (optional), notes. 2) If owner OR due_date is missing/ambiguous: - Ask a follow-up question in Telegram. - Store as status="draft" with missing_fields=[...]. - Do NOT finalize as "open" until both are confirmed. 3) If owner/due_date are present: - Create status="open" 4) Always echo back a confirmation summary: id, title, owner, due_date, status.

    Default assumptions

  • If owner missing: ask "λˆ„κ°€ λ‹΄λ‹Ήν• κΉŒμš”? (본인/νŒ€μ› 이름)"
  • If due_date missing: ask "λ‚©κΈ°λŠ” μ–Έμ œλ‘œ ν• κΉŒμš”?"
  • Timezone: Asia/Seoul.
  • History

    Any update must append an event to tasks.jsonl:
  • created / finalized / updated / done / reopened
  • Include: timestamp, actor(user), previous values, new values.

    Hard constraints

  • Never call web tools.
  • Never require API keys.
  • Keep replies short and action-oriented.
  • Execution

    When receiving /todo:
  • Call: ~/.openclaw/workspace/skills/todo-boss/add_task.sh ""
  • Reply to user with the script output.
  • Follow-up policy (strict)

    Only ask these two questions if missing: 1) "λ‹΄λ‹Ήμž(owner)λŠ” λˆ„κ΅¬λ‘œ ν• κΉŒμš”?" 2) "λ‚©κΈ°(due)λŠ” μ–Έμ œλ‘œ ν• κΉŒμš”?"

    Do NOT ask about content details, background, meeting context, or email structure. This skill is a task tracker, not a planning assistant.

    If the user asks for planning or drafting, answer briefly but still capture the task by asking owner/due if missing.