Task ToDo

v1.0.0

Manage tasks with persistent storage, supporting creation, retrieval, updates, deletion, filtering by status or priority, and status tracking via SQLite.

0· 928·1 current·1 all-time
byManojkumar Kotakonda@makkzone
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description, SKILL.md, and the included Python code all implement a local task/TODO manager using SQLite. There are no unrelated environment variables, binaries, or external services requested.
Instruction Scope
Runtime instructions and the code confine operations to local task management and persistent storage in a local 'tasks.db' file. The SKILL.md does not instruct the agent to read unrelated files, network endpoints, or extra environment variables.
Install Mechanism
No install spec is provided and there are no external dependencies; the code uses Python's built-in sqlite3. Nothing is downloaded or written outside the included files and the local SQLite DB.
Credentials
The skill requires no credentials or environment variables. Its only persistent artifact is a local SQLite DB file (tasks.db), which is proportionate to the stated purpose.
Persistence & Privilege
The skill does not request always:true or other elevated persistence. It creates/uses a database file in the current directory (tasks.db) — expected for local persistence and scoped to its purpose.
Assessment
This skill appears internally consistent and implements a local SQLite-backed task manager. Before installing, consider: (1) The database file tasks.db will be created in the current working directory — avoid running it in directories containing sensitive files and check file permissions. (2) The skill has no network or credential access, so it does not exfiltrate data by design; nevertheless, avoid storing secrets in tasks. (3) If you allow autonomous agent invocation, the agent could create/read/update the local DB automatically — if that is a concern, run the skill manually or in an isolated environment. (4) If you want extra assurance, review or run the code in a sandbox (or a dedicated directory) and delete tasks.db when no longer needed.

Like a lobster shell, security has layers — review code before you run it.

latestvk976kk9g6v1c86aa88mdjgw4xh811grw

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments