topydo
v1.0.5Manage todo.txt tasks using topydo CLI. Add, list, complete, prioritize, tag, and organize tasks with dependencies, due dates, recurrence, and projects. Use for any task management, todo lists, or when the user mentions tasks, todos, or todo.txt. Requires Python 3 and pip. Works on macOS, Linux, and Windows.
⭐ 2· 2.6k·3 current·3 all-time
byTiago Bastos@bastos
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
The name/description (topydo CLI for todo.txt) matches the runtime instructions: commands for add/ls/do/pri/tag/dep/etc. There are no unrelated credentials or binaries requested.
Instruction Scope
Instructions tell the agent (user) to run the topydo CLI and to read/edit todo config and todo files (e.g., ~/.topydo, ~/todo.txt, /etc/topydo.conf). This is expected for a task manager but does mean the skill will operate on user files and may open an editor or write archive files.
Install Mechanism
The skill is instruction-only (no install spec). It suggests standard install methods (brew, pip, apt). That is low-risk for the skill itself, but installing third-party packages via pip/brew should be verified because the skill's registry entry lacks a homepage or source URL.
Credentials
No environment variables or credentials are requested. The instruction set references local config paths and the user’s todo files (appropriate for purpose).
Persistence & Privilege
always is false and the skill is user-invocable; it does not request persistent system privileges or modify other skills. Normal autonomous invocation is allowed by platform defaults.
Assessment
This skill is just documentation for using the topydo CLI and is internally consistent with that purpose. Before following its install suggestions: 1) verify the topydo package/source (homepage or repository) — the skill metadata doesn't include one; 2) prefer installing from trusted package sources (official brew formula, PyPI package with a known maintainer) and inspect the package if you have doubts; 3) be aware topydo will read/write files like ~/todo.txt, ~/.topydo, and /etc/topydo.conf and may open your editor or create output files (e.g., deps.png) — back up sensitive todo data if needed; 4) avoid running pip install commands with sudo unless you trust the package; 5) if you want higher assurance, inspect the topydo project's source repository before installing. Overall the skill is coherent with its stated purpose, but verify upstream before executing installs.Like a lobster shell, security has layers — review code before you run it.
latestvk9787psjacgq6rtssbqnpzxcrx804wwktodovk979yb57qwt8afkd9fme7pnjf17z3ny6todo-txtvk979yb57qwt8afkd9fme7pnjf17z3ny6todo.txtvk979yb57qwt8afkd9fme7pnjf17z3ny6topydovk979yb57qwt8afkd9fme7pnjf17z3ny6
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
