Investigate OpenClaw Gateway failures using read-only checks of configuration, credential references, channels, logs, and ports. Produce findings supported by evidence and recommend a next action without changing configuration or restarting services.
Diagnose Gateway, config, secrets, channels, and port failures with read-only one-liners.
diagnose-gateway investigates OpenClaw Gateway failures through configuration validation, status checks, and log reading. It checks configuration errors, SecretRef credential references, expired channel authentication, port conflicts, and startup crashes. It compares timestamps to locate the first failure, then summarizes the evidence and recommended next action.
Use it to understand a Gateway startup failure or channel connection problem before making repairs. If required logs or access are unavailable, it reports what could not be checked and why, without declaring an unsupported cause.
OpenClaw commands and access to the relevant status information and logs are required. The skill does not change configuration, restart services, or migrate state. Diagnostic commands may still create log or cache records. It reports credential reference status without printing secret values. It uses doctor --lint; repair with doctor --fix --non-interactive is treated as a separate action requiring approval.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI rated this skill on four points using only the contents of its SKILL.md. Stars and popularity are not taken into account.
The total counts each point as A = 25, B = 15, C = 5. Rated by AI (OpenAI Codex) as of Oct 19, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
This playbook is read-only: no config writes, no service restarts, no doctor --fix, no killing listeners. Never print secret values; report only redacted SecretRef owner state. Every run ends with the observable Prove result or an exact explanation of why it could not be proven.
openclaw doctor --lint
openclaw gateway status --deep
openclaw config validate
openclaw channels status
openclaw models status
openclaw channels logs --channel <id>
doctor --lint is read-only and can exit 1 for findings: read the report and continue the remaining checks. Do not substitute ordinary doctor or doctor --non-interactive; they can copy legacy config and migrate state without --fix.
On managed installs, bounded recent logs: ./scripts/clawlog.sh (repo checkout) or the log path printed at gateway startup (/tmp/openclaw/openclaw-<date>.log by default).
Check these signatures without guessing:
config validate names the exact key and line);channels status per account);EADDRINUSE, a second gateway listener, or service/config port mismatch (lsof -nP -iTCP:<port> -sTCP:LISTEN);Correlate timestamps and identify the first owner-boundary failure.
Nothing. Do not change config, migrate state, or alter services. Diagnostic commands may still produce incidental logs or cache bookkeeping.
Translate each finding into the next action, naming the responsible skill when one exists: configure-channel, add-model-provider, or cloud-image-bake. Recommend openclaw doctor --fix --non-interactive only as a separately approved step.
Repeat the smallest read-only check that exposes the condition and record its output, for example:
openclaw gateway status --deep
openclaw channels status --probe
If access, logs, or the gateway are unavailable, report that exact blocker rather than declaring a cause.
Findings in causal order with evidence for each; current gateway/config/SecretRef/channel/port state; one recommended next skill or operator action. State explicitly that no config/service repairs or state migrations were performed.
Further reference: https://docs.openclaw.ai/gateway/troubleshooting
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Set up and authenticate the 1Password CLI, then supply stored passwords and API keys to commands or configuration. The skill covers desktop integration, service accounts, and interactive sign-in while keeping secrets out of chat and logs.
Route requests from OpenClaw to external coding agents such as Claude Code or Cursor. Start or continue sessions using ACP, a protocol for connecting agents, or relay prompts directly through acpx while preserving conversation context.
Add a model provider to OpenClaw and verify it with a real response. The skill validates configuration, keeps credentials in environment or file references, and reports test results and any default model changes.
Prepare an agent activity transcript for a GitHub pull request or issue. Extract relevant prompts, decisions, and results from local logs, remove sensitive material, and preview the edited record before separately authorized publication.
Manage Apple Notes on macOS through memo, a command-line tool. Create, browse, search, edit, delete, and move notes between folders, or export selected notes to HTML or Markdown for use outside the app.
Manage Apple Reminders from your Mac with remindctl, a terminal tool. View tasks by date, add or edit reminders, organize lists, and mark tasks complete or delete them, including personal to-dos that sync to iOS.