Experience Distiller
v0.1.1Distill finished work into the right OpenClaw knowledge layer. Use when a task, fix, setup, integration, cron/report workflow, repeated operation, or output-...
⭐ 0· 84·0 current·0 all-time
byjimmyhe@traceme
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description and the bundled reference files all focus on deciding where to store post-task knowledge (daily logs, experience bank, playbooks, skills). There are no unrelated env vars, binaries, or install steps requested — the requested capabilities are proportionate to the stated purpose.
Instruction Scope
SKILL.md and references clearly define the decision logic and expected outputs. The only runtime-authorized side-effect is: 'If asked to execute, write the files directly.' That is coherent for a knowledge-routing skill, but it means the agent may create/update files under memory/, playbooks/, skills/ etc. The instructions do not instruct reading unrelated system files or exfiltrating data.
Install Mechanism
Instruction-only skill with no install spec and no code files. This is low-risk: nothing is downloaded or written at install time.
Credentials
No environment variables, credentials, or config paths are required. The skill does refer to repository paths (memory/, playbooks/, skills/) but does not request unrelated secrets or external service keys.
Persistence & Privilege
The skill is not marked 'always' and can be invoked by users or autonomously per platform defaults. It explicitly allows writing files when asked, which is consistent with its purpose but does grant persistence (modifying knowledge files). Confirm that the agent's file-write permissions are appropriately scoped before enabling automatic execution.
Assessment
This skill is internally consistent and does not request external credentials or installs. However, it can create or update knowledge files (memory/, playbooks/, skills/) if you ask it to execute — make sure you are comfortable giving the agent write access to those directories. Recommended precautions: (1) run it in a test/sandbox environment first, (2) require human review before allowing it to execute writes automatically, and (3) avoid including secrets in the task/result text you send to the skill so they don't get persisted into knowledge files.Like a lobster shell, security has layers — review code before you run it.
latestvk97ejs8wb1g52n5nvf52q3z6es8398rp
License
MIT-0
Free to use, modify, and redistribute. No attribution required.