smoke-test

Name: smoke-test
Availability: InStock
Author: sigmacodeat

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

Updated Jun 20, 2026

Search Tags:#health check #service recovery #smoke test #openclaw #gbrain #container restart

Ready to run

npx skills add https://github.com/Sigmacodeat/subsumio-web --skill smoke-test-sigmacodeat

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: smoke-test
Source: https://github.com/Sigmacodeat/subsumio-web/tree/main/server/skills/smoke-test
Command: npx skills add https://github.com/Sigmacodeat/subsumio-web --skill smoke-test-sigmacodeat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents broken environments after container restarts by automatically checking critical gbrain and OpenClaw services, identifying failures, and applying known fixes before reporting status.

Core Features & Use Cases

Post-restart health validation: Runs core checks for runtimes, databases, workers, gateways, integrations, and required configuration.
Automatic recovery workflows: Applies tested fixes for known issues and verifies that repairs succeed before reporting.
Extensible smoke testing: Supports custom user-defined checks for additional services and deployment-specific requirements.

Quick Start

Run the smoke-test skill to verify that the environment is healthy after a container restart.

Frequently Asked Questions about smoke-test

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

FAQPage Schema

How do I verify service health after a container restart?▼

A post-restart smoke test automatically verifies service health by checking critical runtimes, databases, and gateways, then reports their operational status after a container restart.

What does a post-restart smoke test check for in OpenClaw and gbrain environments?▼

A post-restart smoke test for OpenClaw and gbrain environments checks core runtimes, databases, workers, gateways, integrations, and required configuration to ensure full service recovery.

Can I automatically repair known service failures after an environment restart?▼

Yes, you can automatically repair known service failures after an environment restart. The smoke test applies tested, idempotent fixes and verifies that the repairs succeed before reporting status.

How do I add custom health checks for my specific deployment requirements?▼

You can add custom health checks for specific deployment requirements by utilizing the extensible smoke testing framework, which supports user-defined validation scenarios alongside core service checks.

What is included in structured smoke test reporting for service recovery?▼

Structured smoke test reporting for service recovery includes automated test execution results, detected failures, applied idempotent fixes, timeout handling outcomes, and the final verified operational status.