TODO List Pro

Track local todo or work-report items in a SQLite database, including planned work, progress amounts, completion status, deletion, and archiving. Use when Co...

Security Scan

The skill is internally consistent: it provides a local Python CLI to manage todos stored in a local SQLite file and does not request unrelated credentials, network access, or unusual installs.

Purpose & Capability

Name/description match the included assets: a Python script plus docs to manage a local SQLite-backed todo/work-report store. Required resources (none) align with a local CLI tool; the only configurable item is TODO_LIST_DB_PATH which coherently maps to the described database override for tests or custom setups.

Instruction Scope

SKILL.md instructs the agent to run the shipped script ({baseDir}/scripts/todo_list.py) and operate on a local DB (~/.work_report_summary/todo_list.db). It documents mapping from natural language to deterministic CLI calls and requires an explicit confirmation for deletions. There are no instructions to read or transmit unrelated system files or to call external endpoints.

Install Mechanism

No install spec is provided (instruction-only behavior), and the package includes a Python script. Nothing in the manifest attempts to download or execute remote code during install. Running the script will create a local directory and SQLite file as expected.

Credentials

No credentials or sensitive environment variables are requested. The only environment variable referenced is TODO_LIST_DB_PATH to override the DB location, which the docs justify (tests/custom setups). No unrelated secrets or external service tokens are required.

Persistence & Privilege

The skill does not request always:true or other elevated/always-present privileges. It writes a local SQLite database under the user's home directory (or an overridden path), which is appropriate for a local todo manager.

Assessment

This skill appears coherent and safe for local use: it runs a Python CLI and stores data in ~/.work_report_summary/todo_list.db by default (you can override with TODO_LIST_DB_PATH). Before installing or enabling it, review the full scripts/todo_list.py (verify there are no unexpected network calls, subprocess/spawn of untrusted commands, or file reads outside its database path). Be aware it will create and modify a local SQLite file; if you want isolation, point TODO_LIST_DB_PATH to a test file first. The skill requires explicit confirmation for permanent deletes, which is good practice.

todo_list

Use this skill to persist local work items instead of keeping them only in chat context.

Workflow

• Run commands from {baseDir}/scripts/todo_list.py.
• Store data in ~/.work_report_summary/todo_list.db by default.
• Override the database path with TODO_LIST_DB_PATH only for tests or when the user explicitly wants a different file.
• Prefer --json whenever the command output will be used in a follow-up step.
• Keep completed items visible in active lists until the user asks to archive them.
• Treat archived items as terminal history. Do not update their progress after archiving.
• Use delete only when the user explicitly wants permanent removal. Prefer archive when the user means "move to history".
• Before running delete, ask for one more explicit confirmation from the user. Permanent deletion should be confirmed, not inferred.

Natural-Language Patterns

Map common user requests to the deterministic CLI instead of keeping task state only in conversation memory.

• Add planned work when the user says things like: 帮我记一下今天要做周报 新增一个任务：整理 demo，计划 3 步 记个 todo：修登录页 bug
• Update progress when the user says things like: 这个任务我做了 2 步 把周报进度更新到 60% 这个任务今天先完成一半
• Mark complete when the user says things like: 这个任务做完了 把第 3 个任务标记完成 周报已经完成
• List or review current work when the user says things like: 看看我现在还有什么没做 列出今天的 todo 我有哪些已经完成但还没归档的任务
• Summarize when the user says things like: 汇总一下我今天做了多少 看下整体进度 给我一个当前完成情况
• Archive only when the user explicitly asks to archive or move finished work into history: 把这个任务归档 把已完成任务都归档
• Delete only when the user explicitly asks to permanently remove a task: 把这个任务删掉 永久删除第 3 个任务 这个 todo 不要了，直接删除
• If the user asks to delete, confirm once more before actually deleting.

When the user does not specify an exact task id, identify the task by title or recent context first, then run the CLI with the resolved id.

Core Commands

• Add a task: python {baseDir}/scripts/todo_list.py --json add --title "Prepare weekly report" --planned-amount 3 --unit sections --details "Collect wins and blockers"
• Record progress: python {baseDir}/scripts/todo_list.py --json progress --id 1 --increment 1 --note "Finished the metrics section"
• Mark a task complete: python {baseDir}/scripts/todo_list.py --json complete --id 1
• List active tasks: python {baseDir}/scripts/todo_list.py --json list --status active
• Archive a task: python {baseDir}/scripts/todo_list.py --json archive --id 1
• Archive by exact title: python {baseDir}/scripts/todo_list.py --json archive --title "Prepare weekly report"
• Archive all completed tasks: python {baseDir}/scripts/todo_list.py --json archive --all-completed
• Delete a task permanently: python {baseDir}/scripts/todo_list.py --json delete --id 1 --confirm
• Delete by exact title: python {baseDir}/scripts/todo_list.py --json delete --title "Prepare weekly report" --confirm
• Summarize progress: python {baseDir}/scripts/todo_list.py --json summary

References

• Read {baseDir}/references/commands.md for full CLI shapes and example flows.
• Read {baseDir}/references/chat_reference.md for natural-language examples and intent-to-command mapping.
• Read {baseDir}/references/storage.md when changing the SQLite schema, default path, or environment-variable behavior.