skills.rest
starlink-awaken
starlink-awakenCOMMUNITY
Explore all skills by this author →
GitHub

smoke-test

Run automated post-restart health checks and self-healing for gbrain and OpenClaw environments.

Updated Jun 10, 2026
Search Tags:#automation#self-healing#health-check#smoke-test#openclaw#gbrain
One-click install
npx skills add https://github.com/starlink-awaken/omostation-gbrain --skill smoke-test-starlink-awaken
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: smoke-test
Source: https://github.com/starlink-awaken/omostation-gbrain/tree/main/skills/smoke-test
Command: npx skills add https://github.com/starlink-awaken/omostation-gbrain --skill smoke-test-starlink-awaken

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the instability of complex environments by automating post-restart verification and self-healing for the gbrain and OpenClaw ecosystem.

Core Features & Use Cases

  • Automated Health Verification: Runs a suite of 8 critical tests to ensure services, databases, and dependencies are operational after a container restart.
  • Self-Healing: Automatically detects and fixes common issues like missing dependencies or broken module paths before reporting status.
  • Extensibility: Allows users to drop custom shell scripts into a designated directory to extend the test suite for specific infrastructure needs.

Quick Start

Run the smoke test skill to verify the current environment health and automatically fix any detected issues.

Frequently Asked Questions about smoke-test

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

FAQPage Schema
How do I automate health checks after a container restart?▼

Automated health checks validate post-restart environment stability by running diagnostic tests on services, databases, and dependencies to ensure full operational readiness.

How does self-healing fix broken module paths and missing dependencies?▼

Self-healing detects missing dependencies or broken module paths during diagnostic testing and automatically applies idempotent fixes to the local runtime before reporting status.

Can I add custom shell scripts to extend the diagnostic test suite?▼

You can extend the diagnostic test suite by dropping custom shell scripts into a designated directory, allowing tailored verification for specific infrastructure requirements.

What's the best way to verify gbrain and OpenClaw configuration integrity?▼

Configuration integrity verification for gbrain and OpenClaw environments is handled by running a suite of eight critical tests targeting dependency verification and service validation.

Do I need shell execution capabilities to run post-restart system validation?▼

Shell execution capabilities are required to run health scripts and apply idempotent fixes to the local runtime during post-restart system validation and dependency verification.

Why does self-healing report issues after an automatic fix is applied?▼

Self-healing reports status only after attempting to detect and automatically fix common issues like missing dependencies, ensuring the local runtime reflects the applied idempotent fixes.

Related Skills

Explore More Software Engineering Skills→
NinatuziNinatuzi

smoke-test

Run diagnostic tests and apply self-healing fixes for gbrain and OpenClaw environments.

Community
Advanced
SigmacodeatSigmacodeat

smoke-test

Verify and repair gbrain and OpenClaw service health after container restarts.

Community
Advanced
stackconsultstackconsult
2

observability-integration

Integrate Sentry, health checks, and centralized logging into Node.js/Express services.

Community
Advanced
beyonaibeyonai
45

smoke-test

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

Community
Advanced