smoke-test

Run post-restart smoke tests for gbrain and OpenClaw health with auto-fixes.

5|1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/GYF0311/lorekit --skill smoke-test-gyf0311
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: smoke-test
Source: https://github.com/GYF0311/lorekit/tree/main/brain/skills/smoke-test
Command: npx skills add https://github.com/GYF0311/lorekit --skill smoke-test-gyf0311

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

It prevents broken container restarts from silently degrading gbrain and OpenClaw by running health checks and applying known safe auto-fixes before you notice.

Core Features & Use Cases

  • Post-restart health verification: Runs 8 core checks to confirm gbrain + OpenClaw components are functioning after a restart.
  • Deterministic auto-fix for known failures: Detects specific issues (e.g., zod/core.cjs missing) and attempts defined remediation, then re-tests to confirm recovery.
  • Extensibility via user drop-ins: Lets you add additional checks by placing executable scripts in ~/.gbrain/smoke-tests.d/*.sh, with results incorporated into the same pass/fail summary.

Quick Start

Run gbrain smoke-test after any container restart to get a pass/fail summary and auto-fix known problems.

Frequently Asked Questions about smoke-test

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

FAQPage Schema
How do I verify container health after a restart?

Run post-restart smoke tests to validate gbrain and OpenClaw health automatically. This Skill executes 8 core checks to verify components are functioning, applies safe auto-fixes for known issues, and returns an exit code equal to the number of unfixed failures.

How does auto-fix work for container restart failures?

Auto-fix for container restart failures works by detecting specific known issues like missing zod/core.cjs files, attempting predefined safe remediation actions, and then re-testing components to confirm successful recovery before reporting the final pass or fail status.

Can I add custom health checks to the smoke testing workflow?

Yes, you can add custom health checks to the smoke testing workflow by placing executable scripts in the ~/.gbrain/smoke-tests.d/*.sh directory. These user drop-ins are incorporated into the same pass or fail summary alongside the 8 core checks.

Does smoke testing support logging results to a configured file?

Yes, smoke testing supports logging results to a configured file. The test suite logs the outcomes of all core and drop-in health checks to this file and returns an exit code equal to the number of unfixed failures for automated tracking.

Why do gbrain and OpenClaw services partially break after a container restart?

gbrain and OpenClaw services may partially break after a container restart due to specific known issues like missing zod/core.cjs files. Post-restart smoke tests detect these failures and automatically apply defined remediation to recover the environment before you notice.