ClawHub

OpenClaw Channel Doctor

v1.0.1

Diagnose and fix OpenClaw messaging channel failures across Telegram, Discord, WhatsApp, Slack, and webchat. Use when users report no replies, no active list...

⭐ 0· 93·0 current·0 all-time
byVasili@vassiliylakhonin
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
The name/description match the instructions: all runtime actions are openclaw CLI commands (status, logs, gateway restart, health) and the skill declares the openclaw binary as required. No unrelated binaries, env vars, or config paths are requested.
ℹ
Instruction Scope
Instructions are focused on read-only checks then narrowly-scoped fixes (gateway restart) and request explicit user confirmation before disruptive actions. They instruct collecting log excerpts for escalation bundles and explicitly ask to redact secrets; this is expected for diagnostics but increases the risk that sensitive data could be exposed if redaction is not performed correctly.
✓
Install Mechanism
There is no install spec — the skill is instruction-only and relies on an existing openclaw binary. This is the lowest-risk install profile.
✓
Credentials
The skill requests no environment variables or credentials. Requiring only the openclaw CLI is proportionate to a troubleshooting tool for OpenClaw channels.
ℹ
Persistence & Privilege
The skill is not always-enabled and does not request persistence. It allows model invocation (the platform default). Because the skill includes a gateway restart command, ensure the agent enforces the SKILL.md rule to obtain explicit user confirmation before performing disruptive actions — otherwise autonomous invocation could lead to unintended restarts.
Assessment
This skill is coherent for diagnosing OpenClaw messaging channels: it only runs the local openclaw CLI and asks you to confirm restarts. Before installing, ensure (1) the openclaw binary on the host is the intended tool and you trust the agent to prompt you before running gateway restart, (2) you or the agent will reliably redact sensitive log contents before sharing, and (3) you prefer running these diagnostics with this skill rather than manually. If you don't trust the agent to require explicit confirmation for disruptive actions, do not grant it permission to run commands that restart gateways or change production state, or test in a safe environment first. The skill source is unknown — that's not a technical mismatch, but if you need higher assurance, get this checklist from a known author or run the commands manually.

Like a lobster shell, security has layers — review code before you run it.

latestvk97bb0cg6tqetdwnjt36eyss0h8382h8

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Runtime requirements

🩺 Clawdis
Binsopenclaw

Comments