Task Persistence
v1.1.0Task continuity, session snapshots, and gateway restart recovery. Use when starting long-running tasks (register them), after gateway restart (check for inte...
⭐ 0· 415·3 current·4 all-time
byDaYu@yangdaowan
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
Name/description (task continuity, snapshots, restart recovery) matches the included scripts (task queue, persistence, snapshots, gateway monitor). Required binary (python3) is appropriate. However the distributed README (dist/SKILL.md) lists extra dependencies (psutil, uv, memory-core) and integration points that the actual scripts don't import; this is a documentation/code mismatch rather than immediate malicious behavior.
Instruction Scope
SKILL.md instructs the agent to run CLI scripts under a workspace path and to use {baseDir}. The scripts themselves perform local filesystem reads/writes (task lists, snapshots, gateway state) under a workspace location. There is no network or external endpoint usage, but SKILL.md and the code disagree about the default workspace (SKILL.md shows /workspace; code often defaults to ~/.openclaw/workspace or /home/admin/.openclaw/workspace). That mismatch could cause the skill to write persistent state into an unexpected user directory if OPENCLAW_WORKSPACE is not set as anticipated.
Install Mechanism
No install spec (instruction-only installer) — low install risk. Code files are packaged with the skill and will run under python3; nothing is being downloaded or executed from remote URLs during install.
Credentials
The skill declares no required environment variables but both SKILL.md and code read OPENCLAW_WORKSPACE (fallbacking to different defaults). No other secrets or unrelated credentials are requested. The main proportionality issue is the inconsistent default workspace paths in docs vs code, which could cause writes to the user's home directory (/home/admin/.openclaw/...) if OPENCLAW_WORKSPACE is not set.
Persistence & Privilege
always: false and model invocation not disabled (normal). The skill writes/reads only its own files under the workspace/persistence and tasks directories and does not modify other skills' configuration or request elevated system privileges. Background monitoring (full mode) starts a daemon thread locally — benign but be aware it runs persistently while active.
What to consider before installing
This skill's code matches its stated purpose (task persistence, snapshots, restart recovery) and does not contact external endpoints, but there are a few practical inconsistencies you should consider before installing:
- Default workspace mismatch: SKILL.md shows /workspace as the default, but the Python code falls back to paths like ~/.openclaw/workspace or /home/admin/.openclaw/workspace if OPENCLAW_WORKSPACE isn't set. Set OPENCLAW_WORKSPACE explicitly to a safe directory to ensure files are written where you expect.
- Docs vs code: dist/SKILL.md mentions optional dependencies (psutil, uv, memory-core) that the included scripts do not actually import; this looks like stale or copy-pasted documentation. Expect the packaged scripts to run with the standard library and python3.
- File writes: the skill will create and modify files under the workspace (tasks/, memory/, persistence/, monitor/). If you have sensitive data in your workspace or care about disk usage, inspect the skill directory and run it in a sandboxed workspace first.
- Background monitoring: running the 'full' mode starts a background monitor thread that will persist in the process. That is normal for this functionality but be mindful if you allow autonomous invocation.
Recommended actions before enabling or granting autonomous use:
1. Inspect the packaged scripts (they are included) to confirm behavior (you've already been given them). 2. Explicitly set OPENCLAW_WORKSPACE to a dedicated sandbox directory. 3. Run check-restart/status commands manually to verify outputs. 4. If you want stronger assurance, run the skill in an isolated environment for a short period and confirm no unexpected files are written outside your chosen workspace.
Overall: not obviously malicious, but internal inconsistencies and potentially surprising default paths justify caution.Like a lobster shell, security has layers — review code before you run it.
latestvk97bn1fjqe98mpjy2nx4s78rwn8213b6
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🔄 Clawdis
Binspython3
