Agent Autonomy Kit Zc

Stop waiting for prompts. Keep working.

Security Scan

The skill's stated purpose (make agents proactive) matches its instructions, but the runtime guidance encourages persistent autonomous scheduling and posting to external channels without explicit safeguards, which could lead to unexpected token usage or data leakage.

Purpose & Capability

Name/description (proactive autonomy) align with the SKILL.md and README: the files consistently describe task queues, heartbeats, and continuous operation. Nothing requested (no envs/binaries) contradicts the stated purpose.

Instruction Scope

Runtime instructions tell the agent to read/write local task and memory files, post to team channels (Discord/Slack), and create cron jobs that run without human prompts. That is within the stated purpose but is broad and open-ended ('do meaningful work') and gives the agent discretion to access and transmit task/memory contents to external channels — a possible data-exfiltration or overreach vector without explicit limits or approval steps.

Install Mechanism

Instruction-only skill with no install spec and no code files. No downloads or package installs are requested, minimizing supply-chain risk.

Credentials

The skill declares no required env vars or credentials, but the instructions assume existing channel/config credentials (Discord/Slack, openclaw cron access). The lack of explicit credential requirements is coherent but may be surprising: the agent will use whatever channel/session permissions already exist and could post sensitive data if those channels are configured.

Persistence & Privilege

always:false (good), but the README explicitly provides openclaw cron commands and config snippets that schedule autonomous runs. Installing these cron jobs grants the agent persistent autonomous execution and ongoing token consumption — a high-impact capability that should be controlled and audited.

What to consider before installing

This kit is coherent with its goal (make agents proactive) but it purposely enables persistent autonomous activity. Before installing or using it: 1) Audit what channels (Discord/Slack) your agent can post to and avoid giving access to sensitive channels; 2) Require explicit human approval or strict token/budget limits before creating cron jobs that run without prompts; 3) Test in an isolated session first (use an isolated agent account and non-sensitive task queue); 4) Monitor token usage and set hard stop conditions (sleep/handoff) to prevent runaway costs; 5) Review and sanitize what the agent writes to memory/task files to avoid leaking secrets. If you can, require an explicit capability grant step before enabling scheduled crons or posting to external services — that would materially reduce the risk and could move this assessment toward benign.

Agent Autonomy Kit

Transform your agent from reactive to proactive.

Quick Start

1. Create tasks/QUEUE.md with Ready/In Progress/Blocked/Done sections
2. Update HEARTBEAT.md to pull from queue and do work
3. Set up cron jobs for overnight work and daily reports
4. Watch work happen without prompting

Key Concepts

• Task Queue — Always have work ready
• Proactive Heartbeat — Do work, don't just check
• Continuous Operation — Work until limits hit

See README.md for full documentation.