Analyze Clawdbot logs and diagnostics. Use when the user asks about bot performance, response times, errors, session stats, token usage, API costs, or wants to debug slow responses.
Security Analysis
high confidenceThe skill's files and runtime instructions match its stated purpose (diagnosing Clawdbot performance and logs); it reads local journal and session files (which contain user conversations and cost data) but does not attempt network exfiltration or request unrelated credentials.
The name/description match what the skill actually does: it inspects systemd user journal entries, local log files, and Clawdbot session files to report response times, errors, token usage, and costs. One small mismatch: SKILL.md and the bundle do not declare required CLI tools (jq, journalctl, systemctl, tail, grep), though the instructions and scripts depend on them.
Instructions and included scripts explicitly read journalctl logs and files in $HOME/.clawdbot (sessions JSON and .jsonl session files) and /tmp logs. That is coherent with debugging/diagnostics, but those session files can contain full conversation contents, token counts, and cost details — sensitive data. The scripts only print local results and do not show any network calls or remote endpoints.
There is no install spec (instruction-only + two local scripts). This is the lowest-risk install pattern: nothing is downloaded or written by an installer step. The provided scripts will run locally when invoked.
The skill requests no environment variables or external credentials. It does access user-owned files and systemd user journals, which is appropriate for its purpose but does mean the skill operates on potentially sensitive local data (conversation content, tokens, costs).
always:false and no install actions or configuration changes are requested. The skill does not attempt to modify other skills or persistent agent settings.
Guidance
This skill appears to do exactly what it says — analyze local Clawdbot logs and session files — and the included scripts are readable and run locally. Before installing/using it, consider: 1) These commands read files in ~/.clawdbot and the user journal; those files can contain full conversation text and cost/token data, so only run this skill in a trusted environment. 2) Ensure required CLI tools are installed (jq, journalctl, systemctl, grep, tail, awk). 3) Confirm the service name (clawdbot-gateway.service) and file paths match your system; otherwise commands may fail or return nothing. 4) Because the scripts print sensitive content to stdout, avoid piping their output to remote services or pasting into third-party tools. 5) If you need tighter privacy, inspect or modify the scripts to redact message contents (e.g., only show metadata) before running.
Latest Release
v1.0.0
- Initial release of clawdbot-logs. - Provides commands and instructions to analyze Clawdbot logs, performance, errors, response times, session stats, token usage, and API costs. - Includes quick diagnostic scripts and common troubleshooting patterns. - Documents log locations and filtering methods for efficient debugging.
Popular Skills
Published by @satriapamudji on ClawHub
