openclaw-doctor

Diagnose and fix OpenClaw gateway issues affecting Telegram bots and agent startup.

3|Updated Jul 17, 2024
One-click install
npx skills add https://github.com/Castrozan/.dotfiles --skill openclaw-doctor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openclaw-doctor
Source: https://github.com/Castrozan/.dotfiles/tree/main/agents/skills/openclaw-doctor
Command: npx skills add https://github.com/Castrozan/.dotfiles --skill openclaw-doctor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnose and fix issues in the OpenClaw gateway to ensure Telegram bots respond and agents start reliably.

Core Features & Use Cases

  • Diagnose gateway status and identify misconfigurations affecting bot responsiveness.
  • Inspect logs, systemd/service status, and provider bindings to pinpoint failures.
  • Troubleshoot gateway and Telegram integration across both local user and system services.

Quick Start

From the command line, run the diagnosis workflow to verify gateway status, check config at ~/.openclaw/openclaw.json, review logs, and validate bot tokens.

Frequently Asked Questions about openclaw-doctor

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

FAQPage Schema
How do I diagnose OpenClaw gateway issues affecting Telegram bots?

To diagnose OpenClaw gateway issues, you check the gateway status, validate the config at ~/.openclaw/openclaw.json, and review systemd and journalctl logs to pinpoint bot responsiveness failures.

Why does my Telegram bot not respond when running OpenClaw under systemd?

Your Telegram bot may not respond due to gateway misconfigurations. Inspecting systemd service status and journalctl outputs helps identify whether the gateway or provider bindings are failing.

How do I validate a Telegram bot token during OpenClaw gateway troubleshooting?

You validate a Telegram bot token by testing it directly via the Telegram API during the OpenClaw diagnosis workflow to ensure the gateway can bind and communicate correctly.

What is the best way to troubleshoot OpenClaw agent startup failures?

The best way to troubleshoot OpenClaw agent startup failures is to run a diagnosis workflow that covers gateway status checks, config validation, and log reviews across both user and systemd environments.

Do I need root access to fix OpenClaw gateway config validation errors?

You do not necessarily need root access, because OpenClaw troubleshooting supports both local user and system services, allowing you to read the local JSON config at ~/.openclaw/openclaw.json directly.