outworked.lol
#10 in Workflows#86 overallAll of @verbove’s filed tweets →
86

Steal this: run a weekly AI memory audit. Your chat history is not knowledge. It’s a graveyard. Once a week, have Claude summarize your Claude Code sessions and cluster what you actually asked it to do into 4 buckets: 1. SKILLS Repeatable tasks you still do manually (should become a button) 2. AGENTS Autonomous workflows (research + action, end to end) 3. SCHEDULED TASKS Stuff to cron (recurring, predictable) 4. CLAUDE.md Your repeated preferences + context (the rules you keep retyping) For each item, include: • 1-line description • session id(s) • frequency count • recommended bucket Sort by frequency. Result: your real workflow, not your imagined one. Whatever you repeat becomes automation, docs, or a skill. Copy/paste prompt: “Analyze my Claude Code session logs from the past 7 days. Extract every user request as a single line. Deduplicate similar requests. Cluster into: SKILLS, AGENTS, SCHEDULED TASKS, CLAUDE.md. For each cluster, list: summary, session id(s), frequency, and what to build next. Sort by frequency. End by asking me which session id to expand for full context.”

Weekly AI audit to surface automation opportunities

🔖 000👁 495mo ago
00 of 1000 · 1k–10k followersReach3×0 bookmarks + 2×0 quotes + 1.5×0 replies + 0 likes = 0, against a cap of 1.5k for this league0/600Per viewer0.0% of 49 viewers did something; 5% is full marks0/400Bookmarks weigh most because people save what they intend to reuse. Every part saturates.hide
Bookmarks0
Likes0
Replies0
Quotes0
Views49
League1k–10k followers

Open on X · Boost ♥ · Permanent page

Filed under Workflows by the model because: Weekly AI audit to surface automation opportunities. The rules.

Martijn Verbove on Workflows · Outsmart