skills.rest
hashimiche
hashimicheCOMMUNITY
Explore all skills by this author →
GitHub

health

Manage hal-health sidecar lifecycle and publish live status snapshots to HAL Plus.

29|8|Updated Mar 24, 2026
Search Tags:#status#container#snapshot#sidecar#hal-health#hal-plus
One-click install
npx skills add https://github.com/hashimiche/hal --skill health-hashimiche
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: health
Source: https://github.com/hashimiche/hal/tree/main/internal/skills/data/health
Command: npx skills add https://github.com/hashimiche/hal --skill health-hashimiche

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The HAL health skill centralizes and automates the lifecycle of the hal-health sidecar, ensuring live ecosystem state snapshots are available to HAL Plus and AI clients for accurate product-state queries.

Core Features & Use Cases

  • Create or recreate the hal-health container to generate a fresh ecosystem snapshot.
  • Update snapshots after ecosystem changes outside normal HAL flows, ensuring healthy state data is current.
  • Delete the hal-health container to clean up resources without affecting core product containers.

Quick Start

Use hal health create to initialize the health sidecar and verify the snapshot endpoint is reachable.

Frequently Asked Questions about health

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

FAQPage Schema
How do I manage the lifecycle of a health sidecar container?▼

You can manage a health sidecar container by applying automated workflows to create, update, or delete the instance. This process refreshes ecosystem state snapshots and publishes live status data to connected AI clients.

What is the best way to generate a fresh ecosystem snapshot after infrastructure changes?▼

Generating a fresh ecosystem snapshot requires recreating or updating the health sidecar container. This captures the current infrastructure state and pushes the updated health data to HAL Plus for accurate product-state queries.

How do I clean up sidecar resources without affecting core application containers?▼

Cleaning up sidecar resources without affecting core containers is done by executing a delete workflow on the health sidecar. This removes the monitoring instance while leaving your primary product containers completely untouched.

Does the HAL health sidecar require specific endpoints to publish status snapshots?▼

Yes, the HAL health sidecar requires a reachable endpoint at hal-health:9001 to function. It uses frontmatter-driven behavior and the hal-health image to successfully publish live status snapshots to HAL Plus.

Why do I need a live status snapshot for my containerized applications?▼

A live status snapshot is needed to provide HAL Plus and AI clients with accurate, real-time product-state data. Centralizing this health monitoring ensures your ecosystem state queries return current and reliable information.

What happens if the hal-health container is not reachable at port 9001?▼

If the hal-health container is not reachable at port 9001, snapshot publication to HAL Plus will fail. You must troubleshoot the sidecar lifecycle and verify the endpoint connection to restore live status updates.

Related Skills

Explore More Software Engineering Skills→
michaelalbermichaelalber
2

environment-health

Diagnose Docker container health, service connectivity, and environment issues.

Community
Advanced
TermiX-officialTermiX-official
109

defillama

Query DeFiLlama endpoints for TVL, protocol, yield, and stablecoin data.

Official
Basic
cristoslccristoslc
2

swain-helm

Manage swain-helm bridge lifecycle and watchdog health via CLI.

Community
Advanced
KrismithReddy12KrismithReddy12

qa-only

Test web applications in read-only mode and generate structured bug reports.

Community
Intermediate