Agent skill · data analytics · sundial-org
clawdbot-logs
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.
Why this skill is useful
Adds specific scripts and commands for analyzing Clawdbot logs and performance metrics that the AI wouldn't reliably generate on its own.
What it needs
Requires jq installed locally. About 1k tokens when loaded. Last updated 2026-03-07. 639 stars on the source repository.
What this skill does
Clawdbot Logs & Diagnostics Analyze Clawdbot performance, errors, and session data. Quick Commands Response Times (last N messages) Recent Errors Session Stats Gateway Status Config Validation Log Sources Source Location Contains -------- ---------- ---------- Journal journalctl --user -u clawdbot-gateway.service Session state, errors, tool exec Daily log /tmp/clawdbot/clawdbot-YYYY-MM-DD.log Detailed JSON logs Session file ~/.clawdbot/agents/main/sessions/.jsonl Full conversation, token usage, costs Sessions meta ~/.clawdbot/agents/main/sessions/sessions.json Current session state, model info Common Diagnostics Slow Responses 1. Check response times: scripts/response-times.sh 20 2. Check token count in sessions.json: jq '.["agent:main:main"].totalTokens' ~/.clawdbot/agents/main/sessions/sessions.json 3. If tokens > 30000, run /compact in Telegram or start new session Config Errors API Costs (from session) Useful Patterns Filter journal by category Parse session file for recent messages
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sundial-org/clawdbot-logs