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.
Best use case
clawdbot-logs is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using clawdbot-logs should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/clawdbot-logs/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How clawdbot-logs Compares
| Feature / Agent | clawdbot-logs | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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 ```
Related Skills
clawdbot-workspace-template-review
Compare a Clawdbot workspace against the official templates installed with Clawdbot (npm or source) and list missing sections to pull in, especially after upgrades.
clawdbot-skill-update
Comprehensive backup, update, and restore workflow with dynamic workspace detection
clawdbot-self-security-audit
Perform a comprehensive read-only security audit of Clawdbot's own configuration. This is a knowledge-based skill that teaches Clawdbot to identify hardening opportunities across the system. Use when user asks to "run security check", "audit clawdbot", "check security hardening", or "what vulnerabilities does my Clawdbot have". This skill uses Clawdbot's internal capabilities and file system access to inspect configuration, detect misconfigurations, and recommend remediations. It is designed to be extensible - new checks can be added by updating this skill's knowledge.
clawdbot-security
Security audit and hardening for Clawdbot/Moltbot installations. Detects exposed gateways, fixes permissions, enables authentication, and guides firewall/Tailscale setup.
clawdbot-release-check
Check for new clawdbot releases and notify once per new version.
clawdbot-documentation-expert
No description provided.
clawdbot-cost-tracker
Track Clawdbot AI model usage and estimate costs. Use when reporting daily/weekly costs, analyzing token usage across sessions, or monitoring AI spending. Supports Claude (opus/sonnet), GPT, and Codex models.
clawdbot-backup
Backup and restore ClawdBot configuration, skills, commands, and settings. Sync across devices, version control with git, automate backups, and migrate to new machines.
portfolio-watcher
Monitor stock/crypto holdings, get price alerts, track portfolio performance
portainer
Control Docker containers and stacks via Portainer API. List containers, start/stop/restart, view logs, and redeploy stacks from git.
portable-tools
Build cross-device tools without hardcoding paths or account names
polymarket
Trade prediction markets on Polymarket. Analyze odds, place bets, track positions, automate alerts, and maximize returns from event outcomes. Covers sports, politics, entertainment, and more.