Midlong Term Task Manager
v0.1.0管理和跟踪 AI Agent 中长期任务，支持任务分解、进度更新、延期提醒及每日/每周总结生成。
⭐ 0· 85·1 current·1 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (mid/long-term task manager) align with the provided artifacts: SKILL.md plus three shell scripts that read/write a tasks.json and logs under ~/.openclaw/workspace/.tasks. There are no unrelated env vars, binaries, or network endpoints requested.
Instruction Scope
Instructions and SKILL.md stay within scope: they instruct running the included scripts, adding heartbeat/cron entries, and storing data under ./.openclaw/workspace/.tasks. Note: the scripts persist task data and logs to disk (tasks.json, logs, summaries/weekly reports); the user should be aware that these files are stored locally and accessible to local processes and users with filesystem access.
Install Mechanism
No install spec (instruction-only + bundled scripts). Scripts are plain shell files included in the package — no network downloads, no package installers, and no extracted archives. This is low-risk from an install mechanism perspective.
Credentials
Skill declares no required environment variables or credentials and the code does not attempt to read secrets or unrelated config. It optionally uses jq if installed, which is reasonable for JSON parsing. The number and type of accesses are proportionate to a local task-manager skill.
Persistence & Privilege
always is false and the skill does not request permanent platform-level privileges or modify other skills' configs. It only writes its own task/log files under ~/.openclaw/workspace/.tasks and suggests (user-driven) cron/heartbeat integration.
Assessment
This skill appears safe and coherent for local task tracking, but review before enabling: 1) inspect the included scripts (they are small, readable, and local-only) and confirm you are comfortable with files being created at ~/.openclaw/workspace/.tasks (tasks.json, logs, summaries). 2) Ensure tasks.json will not contain sensitive secrets; store only task metadata. 3) If you enable cron/heartbeat entries, add them manually rather than blindly executing instructions. 4) Consider file permissions (chmod) on the .tasks directory to limit access. 5) The scripts optionally use jq and rely on GNU date extensions on some platforms — test on your OS or adjust for portability.Like a lobster shell, security has layers — review code before you run it.
latestvk97521ykeenp3qbsa2az5270e183w9c3
License
MIT-0
Free to use, modify, and redistribute. No attribution required.