openclaw-tunelisted

# OpenClaw Tune-Up Use this skill to keep kcn's openclaw setup lean. Run it after every `openclaw update`, or as a periodic chore every 1-2 weeks. ## When to invoke - User says `/openclaw-tune` or `优化下 openclaw` - After `openclaw update` (defaults may have shifted; configs may need migration) - When response feels slow / token costs creeping up - When `agents/main/sessions/` looks suspiciously large ## Operating principles 1. **Don't delete, archive first**: move stale files to `/tmp/openclaw-cleanup-<date>/` so they can be recovered for a day 2. **Verify before touching live state**: if openclaw gateway is running, only touch files it doesn't actively hold (use `lsof`) 3. **Real holdings, real data**: never propose changes that hardcode portfolio numbers — `portfolio.json` is the only source of truth 4. **Report what was done** with sizes/counts; never silent fixes ## Checklist ### 1. Disk bloat Big offenders found historically: | Path | What to look for | Action | |---|---|---| | `~/.openclaw/agents/main/sessions/*.bak-*` | Transcript backups, no rotation. One active session can accumulate 100+ files (7MB each = 700MB) | Keep latest 3 per session, archive rest | | `~/.openclaw/agents/main/sessions/*.bak-*` (orphan) | `.bak` file with no matching `.jsonl` (session deleted but backup stayed) | Archive all | | `~/.openclaw/openclaw.json.clobbered.*` | Config corruption snapshots (e.g. 2026-04-25 had 78) | Archive all (the `.last-good` retains canonical state) | | `~/.