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.
Scanned 2/12/2026
Install to Claude Code
npx -y skills add sundial-org/awesome-openclaw-skills --skill clawdbot-logs --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Clawdbot Logs?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/sundial-org-clawdbot-logs)More formats (shields.io, HTML) on the badges page.
---
name: clawdbot-logs
description: 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.
---
# Clawdbot Logs & Diagnostics
Analyze Clawdbot performance, errors, and session data.
## Quick Commands
### Response Times (last N messages)
```bash
scripts/response-times.sh [count]
```
### Recent Errors
```bash
journalctl --user -u clawdbot-gateway.service --no-pager --since "1 hour ago" | grep -iE "(error|fail|invalid)" | tail -20
```
### Session Stats
```bash
scripts/session-stats.sh
```
### Gateway Status
```bash
systemctl --user status clawdbot-gateway.service --no-pager
```
### Config Validation
```bash
cat ~/.clawdbot/clawdbot.json | jq . > /dev/null && echo "Config valid" || echo "Config invalid"
```
## 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
```bash
journalctl --user -u clawdbot-gateway.service --no-pager --since "10 minutes ago" | grep -i "invalid config"
```
### API Costs (from session)
```bash
scripts/session-stats.sh
```
## Useful Patterns
### Filter journal by category
```bash
# Session state changes
journalctl --user -u clawdbot-gateway.service | grep "session state"
# Tool execution
journalctl --user -u clawdbot-gateway.service | grep "\[tools\]"
# Telegram activity
journalctl --user -u clawdbot-gateway.service | grep "\[telegram\]"
```
### Parse session file for recent messages
```bash
tail -20 ~/.clawdbot/agents/main/sessions/*.jsonl | jq -r 'select(.message.role=="user") | .message.content[0].text' 2>/dev/null | tail -10
```
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!