smoke-test

Run automated health checks and self-healing fixes for GBrain and OpenClaw environments.

45|11|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/beyonai/ByClaw --skill smoke-test-beyonai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: smoke-test
Source: https://github.com/beyonai/ByClaw/tree/main/middleware/openclaw/skills/gbrain/references/smoke-test
Command: npx skills add https://github.com/beyonai/ByClaw --skill smoke-test-beyonai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill resolves the uncertainty following container restarts by automatically verifying the health of the GBrain and OpenClaw environment and applying self-healing fixes to known configuration issues.

Core Features & Use Cases

  • Automated Health Verification: Runs a suite of 8 core tests to ensure services, databases, and dependencies are operational.
  • Self-Healing: Automatically detects and repairs common failures like missing dependencies or broken plugin modules.
  • Extensibility: Allows users to drop custom shell scripts into a designated directory to monitor specific infrastructure components.

Quick Start

Execute the smoke test skill to verify the current container health and apply any necessary automated repairs.

Frequently Asked Questions about smoke-test

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

FAQPage Schema
How do I run a smoke test to verify service health after a container restart?

Run an automated smoke test to verify service health after a container restart. It executes 8 core tests to check GBrain and OpenClaw services, databases, and dependencies, then applies self-healing repairs to known configuration failures.

What is automated self-healing for post-restart recovery scenarios?

Automated self-healing detects and repairs common post-restart failures like missing dependencies or broken plugin modules. It targets container environment stability by automatically applying fixes to known configuration issues without requiring manual intervention.

Can I add custom health checks to monitor specific infrastructure components?

Yes, the smoke test supports extensibility by allowing users to drop custom shell scripts into a designated directory. This lets you monitor specific infrastructure components beyond the 8 core tests for GBrain and OpenClaw environments.

Do I need bash execution capabilities to run automated health checks?

Yes, bash execution capabilities are required to perform automated diagnostic health checks. You also need access to local environment configuration paths to verify system stability and dependency integrity for GBrain and OpenClaw.

Why does my OpenClaw environment have broken plugin modules after a restart?

Container restarts often cause broken plugin modules or missing dependencies. The smoke test skill identifies these common failures during its health verification suite and automatically applies self-healing fixes to restore operational stability.