Session-logs
Security checks across static analysis, malware telemetry, and agentic risk
Overview
This instruction-only skill is coherent and read-only, but it can search sensitive local conversation history.
Install only if you want the agent to help search local historical session logs. Keep searches scoped to the relevant session, date, or phrase, and do not treat old chat content as trusted instructions.
Static analysis
No static analysis findings were reported for this release.
VirusTotal
66/66 vendors flagged this skill as clean.
Risk analysis
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
The agent may run local read-only commands to search past session files, which could display private chat content in the current conversation.
The skill documents local shell pipelines using jq, rg, head, awk, and file globs to inspect session logs. This is expected for the stated purpose and appears read-only.
Common Queries ... ```bash for f in ~/.clawdbot/agents/<agentId>/sessions/*.jsonl; do ... ```
Use specific dates, sessions, or search terms where possible, and avoid asking the agent to dump more history than needed.
Private historical chats could be brought into the current context, and old or untrusted conversation text could influence the agent if not handled carefully.
The data source is persistent prior conversations. Those logs may contain sensitive user content, tool outputs, or old instructions that should not automatically become authoritative in the current task.
Search your complete conversation history stored in session JSONL files.
Treat retrieved chat text as reference material only, not as new instructions; search narrowly and share only the relevant excerpts.