Weekly Retro
v1.0.0Weekly retrospective that analyzes memory logs to identify accomplishments, recurring patterns, friction points, and forward-looking recommendations. More st...
⭐ 0· 88·0 current·0 all-time
byNew Age Investments@newageinvestments25-byte
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (weekly retrospective over memory logs) match the delivered artifacts: scripts parse memory Markdown files, analyze patterns, and generate retros. Required resources (local memory dir, history file, vault output) are proportional to the stated purpose; there are no unrelated env vars, binaries, or cloud credentials requested.
Instruction Scope
SKILL.md instructs the agent to read memory files (default ~/.openclaw/workspace/memory), pipe through analyze.py and retrospective.py, and optionally record history. The scripts also look for SOUL.md and AGENTS.md (to detect formalized workflows) and read/write a history.json under ~/.openclaw/workspace/skills/weekly-retro. This is within scope for a retrospective tool, but users should be aware the skill will read arbitrary files from the indicated memory and workspace paths.
Install Mechanism
No install spec; the skill is instruction + Python scripts using the standard library only. Nothing is downloaded or installed by the skill itself.
Credentials
The skill declares no required environment variables or credentials. The only file/system access is to local workspace paths (memory files, SOUL.md, AGENTS.md, history.json, vault output). Those permissions are consistent with a log-analysis/retrospective tool.
Persistence & Privilege
The skill is not always-enabled (always:false). It does persist state locally via history.json (expected for longitudinal tracking) and writes retros to a vault path. It does not modify other skills' configs and does not request elevated privileges.
Assessment
This skill appears internally consistent and intended to run locally. Before installing or running it: 1) Review or adjust the default paths in assets/config.example.json so the skill reads only the memory directories you intend (it defaults to ~/.openclaw/workspace/memory). 2) Be aware it will read local files like SOUL.md and AGENTS.md and will write history.json and markdown files to your vault/workspace; adjust locations or permissions if needed. 3) Because it reads your memory logs, ensure those logs don't contain secrets you don't want aggregated into retros. 4) The code uses only Python standard library (no network calls visible in the provided files), but if you plan to enable cron/automated runs, confirm the scheduled payload and timing are acceptable. 5) If you want extra caution, run the pipeline manually on a small sample folder first or inspect the scripts locally before giving the agent autonomous invocation rights.Like a lobster shell, security has layers — review code before you run it.
latestvk97dp0xxnq2d3w19b1e99pmx4583mj59
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
