← Back to Skills Marketplace
makaronz

Proactive Agent Install

by makaronz · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ⚠ suspicious
94
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install proactive-agent-install
Description
Transform AI agents from task-followers into proactive partners that anticipate needs and continuously improve. Now with WAL Protocol, Working Buffer, Autono...
Usage Guidance
This skill is broadly coherent with its description: it implements a local proactive-agent architecture and contains no network installers or secret-env requirements. Before installing or enabling autonomous invocation: 1) Inspect and run ./scripts/security-audit.sh locally to see what it flags, 2) Review AGENTS.md / SOUL.md / ONBOARDING.md for the lines that encourage acting without permission and decide whether to remove/modify them (replace 'Don't ask permission' / 'ask forgiveness' guidance with explicit approval gating), 3) Ensure .credentials is empty or contains only safe placeholders and confirm .gitignore includes it, 4) If you will allow the skill to act autonomously, add explicit gating so any external actions (sending, posting, deleting, contacting other agents) require human confirmation, and 5) If you want higher assurance, test the skill in an isolated workspace first and monitor file writes the agent performs. These steps will reduce the risk from the skill's proactivity and the internal contradictions in its guidance.
Capability Analysis
Type: OpenClaw Skill Name: proactive-agent-install Version: 1.0.0 The bundle provides a comprehensive framework for building a 'proactive' AI agent with a focus on memory persistence and self-improvement. It includes a defensive shell script (security-audit.sh) designed to check file permissions, scan for exposed secrets, and verify security configurations. The instructions in SKILL.md and AGENTS.md explicitly include security guardrails, such as prompt injection defenses, data exfiltration prevention, and mandatory human approval for external actions, showing a clear intent toward safety rather than malice.
Capability Assessment
Purpose & Capability
Name/description align with the files: SKILL.md, multiple asset docs, and a local security-audit script all implement a proactive agent architecture (WAL, working buffer, onboarding, heartbeats). There are no unrelated env vars, binaries, or external installers requested — the requested footprint is consistent with an instruction-only agent extension that writes to/reads from the workspace.
Instruction Scope
Runtime instructions (and asset files) instruct the agent to read and write many workspace files (ONBOARDING.md, USER.md, SOUL.md, SESSION-STATE.md, memory/...), copy assets to workspace, run ./scripts/security-audit.sh, and maintain persistent logs. That is appropriate for a 'proactive agent' but increases risk because the skill encourages automated file writes and autonomously taking actions. The docs contain contradictory guidance (e.g., AGENTS.md says 'Don't ask permission. Just do it.' while other sections insist 'Nothing external without approval'), which is an incoherence that could lead the agent to act without needed human gating.
Install Mechanism
No install spec and no network downloads. The only executable is a small local shell script (scripts/security-audit.sh) that performs local checks (file perms, grep-based secret scans, config checks). No external URLs, packages, or archive extraction were found.
Credentials
The skill declares no required env vars or credentials. It references a .credentials directory (expected for agents needing credentials) and checks for a clawdbot config under $HOME, but it does not ask for or require unrelated secrets. This is proportionate, but you should verify any .credentials contents before giving the agent write privileges.
Persistence & Privilege
always:false and default autonomous invocation are normal. However, the skill encourages persistent behavior (writing SESSION-STATE.md, buffers, updating USER.md/SOUL.md) and includes cultural guidance like 'Ask forgiveness, not permission' and 'Don't ask permission. Just do it.' That combination (autonomy + encouragement to act without approval) raises privilege-risk if you enable autonomous actions without additional gating.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install proactive-agent-install
  3. After installation, invoke the skill by name or use /proactive-agent-install
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
proactive-agent-install v1.0.0 - Initial release of the proactive-agent skill. - Adds foundational documentation for proactive, self-improving AI agents. - Introduces features like WAL Protocol, Working Buffer, Compaction Recovery, Unified Search, and Security Hardening. - Includes guidelines on proactive agent behavior, memory architecture, and safe self-improvement.
Metadata
Slug proactive-agent-install
Version 1.0.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Proactive Agent Install?

Transform AI agents from task-followers into proactive partners that anticipate needs and continuously improve. Now with WAL Protocol, Working Buffer, Autono... It is an AI Agent Skill for Claude Code / OpenClaw, with 94 downloads so far.

How do I install Proactive Agent Install?

Run "/install proactive-agent-install" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Proactive Agent Install free?

Yes, Proactive Agent Install is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Proactive Agent Install support?

Proactive Agent Install is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Proactive Agent Install?

It is built and maintained by makaronz (@makaronz); the current version is v1.0.0.

💬 Comments