Windowed Autonomy
v1.0.0Time-windowed autonomous task queue. Autonomy works only during specific time windows (e.g., 8 AM - 8 PM UTC), while cron jobs run overnight. Separates conce...
⭐ 0· 647·3 current·3 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 match the actual instructions: the skill coordinates autonomous work during configured time windows and uses local queue/checkpoint files (tasks/QUEUE.md, memory/*, tasks/MODE_HISTORY.md). It does not request unrelated binaries, env vars, or external services.
Instruction Scope
Instructions direct the agent to read and write many workspace files (QUEUE.md, MODE_HISTORY.md, memory/episodic/[today].md, GOALS.md, .learnings). That is consistent with a task queue. Two points to note: (1) the SKILL assumes the agent/runtime can determine 'tokens remaining' and whether the human (RA) is actively messaging — the skill does not specify how to obtain those signals, which is a gap in the doc; (2) the agent is given discretionary authority (urgent override, choosing tasks, updating GOALS.md/.learnings), which is functional but grants broad action within the workspace.
Install Mechanism
Instruction-only skill with no install spec and no downloaded code. Nothing is written to disk by an installer — the only writes are the runtime file operations the instructions describe.
Credentials
The skill requests no environment variables or credentials. The only privileges it needs are read/write access to project workspace files (task and memory files), which is proportionate to its stated purpose.
Persistence & Privilege
always: false and the skill does not request persistent platform-level privileges or modifications to other skills. It does instruct writing to its own workspace files (mode history, memory files), which is expected for this kind of skill.
Assessment
This skill is coherent and appears to do what it says: manage a time-windowed autonomous task queue by reading and writing local task/memory files. Before installing: (1) Confirm you are comfortable with the agent having read/write access to the workspace paths named (memory/, tasks/, GOALS.md, .learnings) and that those files don't contain secrets you don't want persisted; (2) Verify how your agent runtime exposes token-usage and 'human active' signals — the skill assumes those signals exist but doesn't define how to get them; (3) Decide whether you want the 'urgent' override (allows work outside windows) and whether the agent should be allowed to edit GOALS.md or .learnings automatically; (4) Test in a conservative, limited window and review MODE_HISTORY and logs to ensure behavior matches expectations. If you want tighter control, restrict file-permission scope or add an approval step for urgent tasks and edits to goal files.Like a lobster shell, security has layers — review code before you run it.
latestvk973k0wfhb5yvyc4c26857qgss81887r
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
⏰ Clawdis