Agent GTD
v1.1.3Executive function system for AI agents: GTD-style task management, error/learning capture, and periodic self-review using Taskwarrior. Use when: (1) trackin...
⭐ 0· 68·1 current·1 all-time
byLux Sp4rk@lux-sp4rk
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
Name/description (GTD task management + self-review) matches the included files and runtime behavior: Taskwarrior is the primary backend, helper scripts manipulate Taskwarrior/timew and local markdown files. No unrelated credentials or exotic binaries are requested.
Instruction Scope
Instructions and scripts operate on local Taskwarrior/timew data and workspace files (e.g., ops/session_state.md, memory/). They suggest running grep over workspace memory and using a heartbeat file (~/.agent/last_active) if timew is absent. These read local files (expected for the stated purpose) but do mean the agent will inspect local workspace files and user-maintained Taskwarrior data.
Install Mechanism
There is no automated install spec — SKILL.md recommends installing Taskwarrior/timewarrior via platform package managers. The skill is instruction-first with small helper scripts; nothing is downloaded from an untrusted URL or extracted to disk by an installer.
Credentials
No secrets or remote service credentials are requested. The only environment variables referenced are optional mission-time overrides (AGENT_GTD_MISSION_START/END/MAX_SILENCE) used by the vitality check — proportional to the described monitoring function.
Persistence & Privilege
The skill does not request 'always: true' and is user-invocable only. It reads/writes local session and Taskwarrior state but does not modify other skills' configs or request system-wide privileges.
Assessment
This skill is internally consistent with its stated goal of local GTD-style agent management. Before installing or running it:
- Review and run the helper scripts (scripts/*.py, scripts/sleep.sh) manually to see what they do. They call 'task' and 'timew' and read/write local files (e.g., ~/.agent/last_active, ops/session_state.md).
- The runbook references an automated promotion script (promote_learnings.py) but that file is not present in the bundle; if you plan to rely on automated cron jobs, confirm the implementation exists and inspect it.
- If you enable any optional integrations (Pueue bridge, ClawVault, or any Taskwarrior hooks that execute pueue_cmd), audit those components carefully because they can cause background execution of arbitrary commands. The current bundle does not include an auto-execution bridge, but the documentation describes one as a future/adjacent component.
- Run the vitality_check script in a safe environment first; it invokes 'timew export' and 'task active', and its fallback reads ~/.agent/last_active — ensure those paths are acceptable for your setup.
- Consider running this skill in a sandboxed user account or VM until you are comfortable, and ensure your Taskwarrior data is backed up before bulk changes.
If you want narrower assurance, provide the missing promote_learnings.py (if intended) and confirm whether you plan to enable any auto-execution bridges; with that info I can raise confidence to high or flag additional concerns.Like a lobster shell, security has layers — review code before you run it.
latestvk978zrx5954qwn4ym1w8bwypv983skcd
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
