clawdbot-logs

Analyze Clawdbot logs and diagnostics for performance issues and API costs.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/xintuchain/tongtong --skill clawdbot-logs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clawdbot-logs
Source: https://github.com/xintuchain/tongtong/tree/main/skills/clawdbot-logs
Command: npx skills add https://github.com/xintuchain/tongtong --skill clawdbot-logs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, journalctl, systemctl, and includes scripts (resource) components.

What problem does it solve?

Identify and surface performance regressions, slow responses, errors, and session-level metrics for Clawdbot so operators can quickly triage outages and optimize behavior.

Core Features & Use Cases

  • Analyze response times across recent runs to flag slow assistant executions and long-running tool invocations.
  • Aggregate session statistics, token usage, compaction status, and recent API cost summaries from per-session JSON and JSONL files.
  • Inspect system journal and gateway service state to locate configuration errors, tool failures, and Telegram activity that affect bot performance.
  • Use Case: When users report slow replies, run response time analysis, check session token counts, and review recent journal errors to determine if a compaction or new session is needed.

Quick Start

Ask the skill to analyze the last 20 Clawdbot runs, list slow responses and recent errors, and summarize token usage and session cost.

Frequently Asked Questions about clawdbot-logs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze Clawdbot logs to find slow response times and errors?

To analyze Clawdbot logs for slow responses and errors, you parse system journal entries and per-session JSONL files to inspect run timings, tool execution failures, and recent API costs. This skill automates that parsing using journalctl and jq.

How can I check Clawdbot token usage and session API costs from the command line?

You can check Clawdbot token usage and session API costs by aggregating data from per-session JSON and JSONL files. The skill uses shell scripts with jq to summarize compaction status and recent API cost summaries directly from the file system.

Do I need journalctl and systemctl to troubleshoot Clawdbot performance issues?

Yes, you need journalctl and systemctl to troubleshoot Clawdbot performance issues effectively. The skill requires these dependencies to inspect the system journal and gateway service state for configuration errors and Telegram activity affecting bot performance.

What is the best way to diagnose a Clawdbot production outage from system logs?

The best way to diagnose a Clawdbot production outage is to review the system journal for configuration errors and tool failures. This skill inspects gateway service states and recent journal errors to quickly triage outages and identify performance regressions.

Why is Clawdbot not responding and how do I review its journal errors?

If Clawdbot is not responding, you should review its journal errors to locate configuration issues or long-running tool invocations. This skill analyzes the system journal and daily JSON logs to surface these specific performance bottlenecks.

Can I use jq to parse JSONL session files for Clawdbot diagnostics?

Yes, you can use jq to parse JSONL session files for Clawdbot diagnostics. The skill executes helper scripts that rely on jq to aggregate session statistics, compaction status, and token usage from the available session files.