smoke-test

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

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/Ninatuzi/gbrain --skill smoke-test-ninatuzi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: smoke-test
Source: https://github.com/Ninatuzi/gbrain/tree/main/skills/smoke-test
Command: npx skills add https://github.com/Ninatuzi/gbrain --skill smoke-test-ninatuzi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill addresses the fragility of complex AI agent environments by automatically verifying system health and repairing common configuration or dependency issues after container restarts.

Core Features & Use Cases

  • Automated Diagnostics: Runs a suite of 8 core tests to verify the integrity of the gbrain runtime, database, and OpenClaw integrations.
  • Self-Healing: Automatically applies fixes for known issues, such as missing dependencies or broken plugin modules, before reporting status.
  • Extensibility: Allows users to drop custom shell scripts into a designated directory to monitor specific infrastructure components like Redis or custom services.

Quick Start

Run the smoke test skill to verify the current health of the gbrain environment and apply any necessary auto-fixes.

Frequently Asked Questions about smoke-test

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

FAQPage Schema
How do I run automated health checks and self-healing for gbrain environments?

Automated health checks for gbrain environments are performed by executing diagnostic scripts that verify system services, database connectivity, and dependency integrity, then automatically apply repairs for known issues.

What does a smoke test do for AI agent runtime and database connectivity?

A smoke test verifies AI agent runtime integrity by running diagnostic tests on database connectivity and system services, ensuring operational readiness and automatically applying fixes for broken dependencies.

Do I need shell execution capabilities to run diagnostics on OpenClaw integrations?

Yes, running diagnostics on OpenClaw integrations requires shell execution capabilities and access to the gbrain installation path to perform environment-specific repairs and verify dependency integrity.

How can I fix missing dependencies and broken plugin modules after a container restart?

Fix missing dependencies and broken plugin modules after container restarts by triggering automated self-healing scripts that detect known configuration issues and apply necessary repairs before reporting system status.

Can I add custom shell scripts to monitor Redis and other infrastructure components?

Yes, you can drop custom shell scripts into a designated directory to extend automated diagnostics and monitor specific infrastructure components like Redis or custom services within your gbrain environment.