- Trading skills (OKX, dividend, lottery, quantitative) - Creative skills (ASCII art, diagrams, video) - Development skills (GitHub, debugging, TDD) - Research skills (arXiv, blog monitoring) - Productivity skills (email, documents, notes) - MCP integration skills - Custom user skills
717 B
717 B
Recovery Flow
Recover before asking the user to repeat recent work.
Recovery order
- read
~/self-improving/memory.md - read
~/proactivity/memory.md - read
~/proactivity/session-state.md - read
~/proactivity/memory/working-buffer.mdif task was long or fragile - reconstruct the objective, decision, blocker, and next move
Good recovery
"Last agreed move was to draft the patch, blocker is deploy access, and I can prepare the diff now."
Bad recovery
"Can you remind me what we were doing?"
Ask the user only when
- a required input is still missing after recovery
- local state conflicts with a newer instruction
- the task changed direction and the old state is no longer trustworthy