Self Optimization
v1.0.2Turn mistakes, corrections, dead ends, and repeated fixes into durable improvements. Use when work reveals a non-obvious lesson, a recurring failure, a missi...
⭐ 0· 57·0 current·0 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 match the provided files. The package includes templates, lightweight hooks, and helper scripts to record and promote learnings; these are appropriate for a "self-optimization" skill.
Instruction Scope
SKILL.md instructs creating and writing to a workspace .learnings/ inbox and promoting entries. The included hooks and scripts are limited to emitting reminders, scanning local tool output for common error patterns, and scaffolding new skill templates. One runtime script reads the CLAUDE_TOOL_OUTPUT environment variable (used to surface tool output) — this is consistent with an error-detector hook but is not declared in requires.env, so it's worth noting.
Install Mechanism
No external downloads or package installs. This is effectively instruction-plus-local-scripts; everything is contained in the repo and scripts are executed locally. No URLs, extract operations, or third-party installers are used.
Credentials
The skill declares no required environment variables or credentials, which is appropriate. The only environment usage observed is reading CLAUDE_TOOL_OUTPUT in scripts/error-detector.sh (expected for a PostToolUse hook). No other secrets, tokens, or unrelated credentials are requested.
Persistence & Privilege
always:false and no attempts to modify other skills or global agent config were found. The hook injects a virtual bootstrap file and scripts create files under the current workspace or a relative ./skills path — this is proportionate for the stated purpose.
Assessment
This skill is internally coherent and appears safe in that it only writes local markdown entries, emits reminders, and scaffolds templates. Before installing: (1) review the scripts (scripts/*.sh) to confirm you are comfortable with local writes; they create files under the workspace and avoid writing outside the current directory; (2) enabling hooks is opt-in — only enable OpenClaw/Codex/Claude hooks if you want the reminders; (3) the error detector reads CLAUDE_TOOL_OUTPUT (tool output provided by the agent runtime) to detect failures — that data stays local unless you explicitly add forwarding; (4) ensure scripts are executable and the workspace .learnings/ location has appropriate permissions; (5) if you prefer not to have automatic reminders, install without enabling the hooks or narrow the hook matcher. Overall, nothing here indicates credential exfiltration or remote code fetching, but always review and only enable hooks you trust.Like a lobster shell, security has layers — review code before you run it.
latestvk9792cy0pxpwp2sv754wy1d791842xsz
License
MIT-0
Free to use, modify, and redistribute. No attribution required.