MH session-logs
v1.0.0Search and analyze your own session logs (older/parent conversations) using jq.
⭐ 0· 476·1 current·1 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (search/analyze session logs) match the requested binaries (jq, rg) and the SKILL.md examples. The claimed data location (~/.openclaw/agents/<agentId>/sessions/) and the operations (jq parsing, rg searching) are proportionate to the stated purpose.
Instruction Scope
Instructions explicitly tell the agent to read session JSONL files under the user's home directory and use the agent ID from the system prompt; this is within the skill's purpose but does involve reading potentially sensitive local chat transcripts. The SKILL.md does not instruct reading other system files or unrelated credentials.
Install Mechanism
Instruction-only skill with no install spec or downloaded code; lowest install risk. It assumes jq and rg are already present on PATH.
Credentials
No environment variables, credentials, or external config paths are requested. The access requested (local session files) is consistent with the skill's purpose.
Persistence & Privilege
always:false (default) and no install changes or system-wide config modifications are requested. The skill can be invoked autonomously per platform defaults but it does not request elevated persistence or cross-skill config access.
Assessment
This skill simply provides shell/jq/rg commands to read your OpenClaw session JSONL files. Before installing or invoking it, be aware that: 1) it reads local chat transcripts stored under ~/.openclaw/agents/<agentId>/sessions/, which may contain sensitive data (secrets, PII, private conversations); 2) ensure you trust any agent or automation that will run these commands, or restrict the skill to manual invocation only; 3) install jq and ripgrep (rg) if missing and verify file permissions on the sessions directory; 4) if you don't want older conversations exposed, consider deleting or redacting sensitive sessions or restricting access to those files. If you want a tighter security posture, deny autonomous invocation for this skill or require explicit user consent before reading session files.Like a lobster shell, security has layers — review code before you run it.
latestvk9720zw4bnkq37x4gw7cz9dx1981sfw8
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
📜 Clawdis
Binsjq, rg