How do I install the Clawdbot Logs skill?

Run npx skillmds@latest add modbender/clawdbot-logs in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Clawdbot Logs safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: executes scripts, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Clawdbot Logs?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Clawdbot Logs free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Clawdbot Logs?

modbender (@modbender) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Clawdbot Logs by modbender — Agent Skill

Name: Clawdbot Logs
Rating: 4.2 (5 reviews)
Author: modbender

File contents

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

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

Check response times: scripts/response-times.sh 20
Check token count in sessions.json: jq '.["agent:main:main"].totalTokens' ~/.clawdbot/agents/main/sessions/sessions.json
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

---name: clawdbot-logsdescription: 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 ```

Frequently asked questions

Clawdbot Logs