sessions-manager

v1.0.0

Manage OpenClaw agent sessions - list active/completed sessions, view session details, and delete sessions by ID. Use when you need to inspect session state,...

0· 87·0 current·0 all-time
byJiakai Xu@6eanut
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description match the included CLI tool and its behavior: reading sessions.json and optionally deleting the matching .jsonl history files under ~/.openclaw. No unrelated credentials, binaries, or config paths are requested.
Instruction Scope
SKILL.md explicitly instructs running the included Python script and references the same ~/.openclaw session paths that the script uses. The instructions do not ask the agent to read unrelated files, environment variables, or to transmit data externally.
Install Mechanism
No install spec is provided (instruction-only). The skill includes a small Python script; there are no downloads, package installs, or archive extraction steps.
Credentials
The skill requests no environment variables, credentials, or external configuration. File access is limited to the local ~/.openclaw sessions directory, which is appropriate for a session-management utility.
Persistence & Privilege
The skill is not marked always:true and does not modify other skills or global agent settings. It performs local file deletions only (sessions.json and the matching .jsonl history file), which aligns with its purpose.
Assessment
This skill is coherent and appears to do only what it claims: list sessions and delete session metadata/history under ~/.openclaw. Before installing or running: (1) review and keep a backup of ~/.openclaw/agents/main/sessions/sessions.json if you care about session history, since delete will permanently remove entries and files; (2) run the list command first to confirm which session will be deleted; (3) because the script runs as your user, avoid running it as root to reduce risk; (4) if you don't trust the unknown publisher, inspect the included scripts (they're small and present) rather than executing them blindly. If the skill later requested network access or additional credentials, or if its instructions changed to read other system paths, reassess (that would raise the risk).

Like a lobster shell, security has layers — review code before you run it.

latestvk97b05m0eece68y5q9n1ysmkzs84hnqb

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments