skills$openclaw/clawdbot-logs
satriapamudji7.0k

by satriapamudji

clawdbot-logs – OpenClaw Skill

clawdbot-logs is an OpenClaw Skills integration for coding workflows. 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.

7.0k stars1.8k forksSecurity L1
Updated Feb 7, 2026Created Feb 7, 2026coding

Skill Snapshot

nameclawdbot-logs
descriptionAnalyze 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. OpenClaw Skills integration.
ownersatriapamudji
repositorysatriapamudji/clawdbot-logs
languageMarkdown
licenseMIT
topics
securityL1
installopenclaw add @satriapamudji/clawdbot-logs
last updatedFeb 7, 2026

Maintainer

satriapamudji

satriapamudji

Maintains clawdbot-logs in the OpenClaw Skills directory.

View GitHub profile
File Explorer
5 files
.
scripts
response-times.sh
1.7 KB
session-stats.sh
1.8 KB
_meta.json
285 B
SKILL.md
2.3 KB
SKILL.md

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)

scripts/response-times.sh [count]

Recent Errors

journalctl --user -u clawdbot-gateway.service --no-pager --since "1 hour ago" | grep -iE "(error|fail|invalid)" | tail -20

Session Stats

scripts/session-stats.sh

Gateway Status

systemctl --user status clawdbot-gateway.service --no-pager

Config Validation

cat ~/.clawdbot/clawdbot.json | jq . > /dev/null && echo "Config valid" || echo "Config invalid"

Log Sources

SourceLocationContains
Journaljournalctl --user -u clawdbot-gateway.serviceSession state, errors, tool exec
Daily log/tmp/clawdbot/clawdbot-YYYY-MM-DD.logDetailed JSON logs
Session file~/.clawdbot/agents/main/sessions/*.jsonlFull conversation, token usage, costs
Sessions meta~/.clawdbot/agents/main/sessions/sessions.jsonCurrent 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

journalctl --user -u clawdbot-gateway.service --no-pager --since "10 minutes ago" | grep -i "invalid config"

API Costs (from session)

scripts/session-stats.sh

Useful Patterns

Filter journal by category

# 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

tail -20 ~/.clawdbot/agents/main/sessions/*.jsonl | jq -r 'select(.message.role=="user") | .message.content[0].text' 2>/dev/null | tail -10
README.md

No README available.

Permissions & Security

Security level L1: Low-risk skills with minimal permissions. Review inputs and outputs before running in production.

Requirements

  • OpenClaw CLI installed and configured.
  • Language: Markdown
  • License: MIT
  • Topics:

Configuration

```bash cat ~/.clawdbot/clawdbot.json | jq . > /dev/null && echo "Config valid" || echo "Config invalid" ```

FAQ

How do I install clawdbot-logs?

Run openclaw add @satriapamudji/clawdbot-logs in your terminal. This installs clawdbot-logs into your OpenClaw Skills catalog.

Does this skill run locally or in the cloud?

OpenClaw Skills execute locally by default. Review the SKILL.md and permissions before running any skill.

Where can I verify the source code?

The source repository is available at https://github.com/openclaw/skills/tree/main/skills/satriapamudji/clawdbot-logs. Review commits and README documentation before installing.