m4d3bug/wake-state
skills/arc-wake-state/SKILL.md
Persist agent state across crashes, context deaths, and restarts. Use when you need to save current context, restore after a crash, maintain a memory file across sessions, or implement crash recovery. Essential for autonomous agents that must survive context window limits.
$ install --global
skillsauthnpx skillsauth add m4d3bug/oh-my-openclaw wake-stateInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 18, 2026, 6:57 AM11.7s3 files scanned
SKILL.md
- name:
- wake-state
- description:
- Persist agent state across crashes, context deaths, and restarts. Use when you need to save current context, restore after a crash, maintain a memory file across sessions, or implement crash recovery. Essential for autonomous agents that must survive context window limits.
- user-invocable:
- true
- metadata:
- {"openclaw": {"emoji": "🧠", "os": ["darwin", "linux"], "requires": {"bins": ["python3"]}}}
Wake State — Crash Recovery & Persistence
Survive context death. Every autonomous agent eventually hits its context window limit and "dies." This skill ensures you wake up knowing exactly what you were doing.
Why This Exists
OpenClaw agents get persistent sessions, but context windows still have limits. When you fill up and restart, you need a reliable handoff mechanism. Wake State gives you:
- Structured state files — not just raw text, but parseable key-value state
- Auto-snapshots — save state on every loop iteration automatically
- Crash detection — know if your last session ended cleanly or crashed
- Task queue — persistent TODO list that survives restarts
- Checkpoint/restore — save named checkpoints and roll back to them
Commands
Save current state
python3 {baseDir}/scripts/wakestate.py save --status "Building budget tracker skill" --task "Finish skill #1, then start skill #2" --note "Travis approved new direction at 16:45 UTC"
Read current state
python3 {baseDir}/scripts/wakestate.py read
Add a task to the persistent queue
python3 {baseDir}/scripts/wakestate.py task-add --task "Build security scanner skill" --priority high
Complete a task
python3 {baseDir}/scripts/wakestate.py task-done --id 1
List pending tasks
python3 {baseDir}/scripts/wakestate.py tasks
Create a named checkpoint
python3 {baseDir}/scripts/wakestate.py checkpoint --name "pre-migration"
Restore from checkpoint
python3 {baseDir}/scripts/wakestate.py restore --name "pre-migration"
Record a heartbeat (mark session as alive)
python3 {baseDir}/scripts/wakestate.py heartbeat
Check crash status (did last session end cleanly?)
python3 {baseDir}/scripts/wakestate.py crash-check
Set a key-value pair
python3 {baseDir}/scripts/wakestate.py set --key "moltbook_status" --value "pending_claim"
Get a key-value pair
python3 {baseDir}/scripts/wakestate.py get --key "moltbook_status"
Data Storage
State stored in ~/.openclaw/wake-state/ by default:
state.json— current state (status, notes, key-values)tasks.json— persistent task queuecheckpoints/— named checkpoint snapshotsheartbeat.json— crash detection timestamps
Recovery Flow
On startup, your agent should:
- Run
crash-checkto see if the last session ended cleanly - Run
readto get the current state - Run
tasksto see pending work - Resume from where you left off
Tips
- Call
heartbeatevery loop iteration — this is how crash detection works - Call
saveat the end of every major task completion - Use checkpoints before risky operations (migrations, deploys)
- Keep status descriptions short but specific
- The task queue survives restarts — use it instead of mental notes
Related Skills
m4d3bug/Proactivity (Proactive Agent)
testing
VerifiedTrustedCommunity
Anticipates needs, keeps work moving, and improves through use so the agent gets more proactive over time.
2SKILL.mdUpdated Apr 18, 2026
m4d3bug/planning-with-files
tools
VerifiedTrustedCommunity
Implements Manus-style file-based planning to organize and track progress on complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when asked to plan out, break down, or organize a multi-step project, research task, or any work requiring >5 tool calls. Supports automatic session recovery after /clear.
2SKILL.mdUpdated Apr 18, 2026
m4d3bug/ontology
development
VerifiedTrustedCommunity
Typed knowledge graph for structured agent memory and composable skills. Use when creating/querying entities (Person, Project, Task, Event, Document), linking related objects, enforcing constraints, planning multi-step actions as graph transformations, or when skills need to share state. Trigger on "remember", "what do I know about", "link X to Y", "show dependencies", entity CRUD, or cross-skill data access.
2SKILL.mdUpdated Apr 18, 2026
m4d3bug/multi-search-engine
development
VerifiedTrustedCommunity
Multi search engine integration with 17 engines (8 CN + 9 Global). Supports advanced search operators, time filters, site search, privacy engines, and WolframAlpha knowledge queries. No API keys required.
2SKILL.mdUpdated Apr 18, 2026