OpenClaw Troubleshooter Pro

v1.0.0

Fast, symptom-first troubleshooting for OpenClaw incidents with minimal downtime. Use when OpenClaw is failing or unstable (status unreachable, missing scope...

0· 110·0 current·0 all-time
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
Name/description match the instructions. All commands are openclaw CLI operations and logs/health checks that are appropriate for troubleshooting OpenClaw incidents.
Instruction Scope
Instructions stay within troubleshooting scope (status/health/logs/restarts). They include restart commands and log collection; the SKILL.md explicitly requires explicit confirmation before irreversible or broad changes, which mitigates risk. Verify the agent will actually prompt for confirmation before running restart commands in interactive or automated contexts.
Install Mechanism
No install spec and no code files — instruction-only skill (lowest install risk). Nothing is downloaded or written to disk by the skill itself.
Credentials
The skill requires no environment variables, credentials, or config paths. All operations use the openclaw CLI and its own log/health commands, which is proportionate to the stated purpose.
Persistence & Privilege
always is false. disable-model-invocation is false (default), so the agent could invoke the skill autonomously; because the skill includes restart commands, consider requiring explicit user confirmation or restricting autonomous invocation in sensitive environments.
Assessment
This skill is coherent and appears to do what it claims, but it will run service-restart commands and collect logs via the openclaw CLI. Before installing or using it: ensure the openclaw CLI is the expected trusted binary on your PATH; confirm the agent is configured to require user consent before running restart/irreversible commands (the SKILL.md asks for confirmation but make sure your agent enforces it); be aware that logs may contain sensitive data — limit what you share externally; run troubleshooting in a maintenance window or on a staging instance when possible; and if you want to avoid accidental automated restarts, disable autonomous invocation for this skill or require an explicit confirmation step in your agent policy.

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

latestvk9763307jfkpg581hscgntqsth838017

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments