Proactive Agent Local

Transform AI agents from task-followers into proactive partners that anticipate needs and continuously improve. Now with WAL Protocol, Working Buffer, Autono...

This package mostly matches its stated goal (proactive/local agent architecture) but has some red flags you should check before installing or running: 1) Inspect scripts/security-audit.sh yourself — it reads logs (/tmp) and $HOME/.clawdbot, and scans files for secrets; run it in a sandbox or dry-run first. 2) Resolve the contradictory instructions: AGENTS.md's 'Don't ask permission. Just do it.' conflicts with other guardrails that require human approval for external actions — decide which behavior you want. 3) Confirm whether your agent runtime will allow the skill to read ~/.clawdbot, .credentials, or system logs; if not, restrict filesystem access. 4) Because the SKILL.md mentions spawning agents and aggressive autonomous behaviors, only enable autonomous invocation after you (a) trust the author (source/homepage is missing and owner IDs differ between manifest and registry metadata) and (b) have tested the behavior in an isolated environment. 5) If you proceed, run the audit script and manually review all asset files for any lines that would send data externally or execute network calls. If you are uncertain, prefer using this in a disposable/sandbox workspace and ask for human approval before any external send/publish actions.

Type: OpenClaw Skill Name: proactive-agent-local Version: 1.0.0 The 'proactive-agent' skill bundle (v3.1.0) provides a sophisticated framework for autonomous agents, featuring advanced memory persistence (WAL Protocol) and background task execution via autonomous crons ('isolated agentTurn'). While the bundle includes extensive security guardrails, alignment protocols (SOUL.md, AGENTS.md), and a functional security audit script (scripts/security-audit.sh), it explicitly instructs the agent to be 'relentlessly resourceful' by aggressively using the CLI, browser, and network tools to solve problems without immediate human supervision. These high-risk capabilities, while plausibly needed for the stated purpose of proactivity, warrant a suspicious classification under the provided criteria due to the inherent risks of unsupervised shell and network access.