Openclaw Proactive Agent Lite
v1.0.0Transform AI agents from task-followers into proactive partners with memory architecture, reverse prompting, and self-healing patterns. Lightweight version f...
⭐ 0· 180·2 current·2 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name and description (proactive behavior, memory, reverse prompting, self-healing) match the provided README and SKILL.md content. There are no unexpected required binaries, env vars, or config paths that would be unrelated to a behavior/architecture-level skill.
Instruction Scope
SKILL.md and README are prose only: they contain high-level patterns and claims but no runtime commands, file reads, or external endpoints. The instructions are intentionally vague ('Simply install and the agent will automatically begin exhibiting proactive characteristics'), which gives broad behavioral discretion to the agent but does not itself perform or request sensitive actions.
Install Mechanism
No install spec or code files are present (instruction-only). The README shows a 'clawhub install' example but there are no downloads, archives, or third-party package installs to evaluate.
Credentials
The skill declares no required environment variables, credentials, or config paths. There are no requests for unrelated secrets or system access in the provided documents.
Persistence & Privilege
Skill flags are default (always: false, user-invocable: true, model invocation allowed). Autonomous invocation is permitted by platform default; combined with the skill's vague operational description this means you should monitor its behavior after enabling it, but there are no additional privilege requests or 'always: true' present.
Assessment
This skill is an instruction-only add-on that makes high-level claims but provides no code or resource requests — that makes it internally consistent but also vague. Before installing: (1) be prepared to monitor agent actions after enabling the skill (start with low-privilege agents or sandboxed usage), (2) do not grant any credentials or external integrations unless you understand exactly why they're needed, and (3) if you want stronger assurance, request the skill's implementation details or an install script so you can review any network activity or file/system access it would perform. If the agent begins making unexpected external calls or asking for credentials, disable the skill and investigate.Like a lobster shell, security has layers — review code before you run it.
latestvk973qq15zx79ja45cpr0r3ch8s83yjvx
License
MIT-0
Free to use, modify, and redistribute. No attribution required.