Agents Refresh MD v1.1.2 🐾
v1.1.2AGENTS.md/IDENTITY/SOUL/USER periodic reload skill to keep context fresh (.md-only v1.1.2). Prevents confusion and forgetting in long sessions. Edit HEARTBEA...
⭐ 0· 345·2 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, manifest permissions (read: AGENTS.md, SOUL.md, IDENTITY.md, USER.md, memory/*.md; write/edit: MEMORY.md, HEARTBEAT.md) and the SKILL.md instructions align: the skill only reads agent state and distills entries into MEMORY.md.
Instruction Scope
SKILL.md instructs the agent to read the files referenced in the manifest, summarize/distill '4 Golds', edit HEARTBEAT.md, and add/run cron jobs. These actions stay within the declared purpose and declared file permissions. Note: it assumes platform tools like cron, edit, and session_status are available.
Install Mechanism
There is no install spec and no code files; this is an instruction-only skill. Nothing is written to disk by an installer and nothing is downloaded, which is low-risk.
Credentials
The skill requests no environment variables or credentials. The manifest permission set is limited to the Markdown files needed for its function and is proportionate to the stated task.
Persistence & Privilege
always:false (not globally forced), but the skill and manifest promote adding a scheduled cron job that will run periodically and trigger the refresh task autonomously. This is expected for a scheduler-based memory refresher, but it does grant recurring autonomous runs that will read/write agent memory files—users should be aware.
Assessment
This skill is coherent with its purpose: it will read your agent's AGENTS.md, SOUL.md, IDENTITY.md, USER.md and memory/*.md and write distilled notes to MEMORY.md and HEARTBEAT.md. Before installing, (1) ensure those Markdown files do not contain secrets or sensitive external credentials, (2) confirm you are comfortable with a scheduled cron job that will autonomously trigger these reads/writes, and (3) verify your platform's cron/edit/session_status tools behave as you expect (e.g., whether scheduled jobs require explicit approval or can run without further consent). If you want only manual runs, skip adding the cron job or remove the schedule entry from the manifest. If you need more assurance, inspect HEARTBEAT.md and MEMORY.md outputs after the first manual run before enabling automation.Like a lobster shell, security has layers — review code before you run it.
latestvk97c9bqqxge8x1vey1mz1k7019822k6t
License
MIT-0
Free to use, modify, and redistribute. No attribution required.