adame-s6-container-supervision

Manage s6-overlay supervision trees and container boot reconciliation for Adame Agent Docker images.

9|Updated Jul 1, 2026
One-click install
npx skills add https://github.com/Cyapstaye/Adame_ver.open --skill adame-s6-container-supervision
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adame-s6-container-supervision
Source: https://github.com/Cyapstaye/Adame_ver.open/tree/main/skills/software-development/hermes-s6-container-supervision
Command: npx skills add https://github.com/Cyapstaye/Adame_ver.open --skill adame-s6-container-supervision

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the complexity of managing service lifecycles and process supervision within the Adame Agent Docker environment, ensuring reliable container behavior and profile gateway persistence.

Core Features & Use Cases

  • Service Supervision: Manage static services and per-profile gateways using s6-overlay v3.2.3.0.
  • Boot Reconciliation: Automatically restore profile gateway states and permissions on container startup.
  • Architecture Guidance: Provides deep insights into the main-wrapper.sh pattern, allowing developers to safely extend the container without breaking the s6 supervision tree.

Quick Start

Use the adame-s6-container-supervision skill to inspect the status of all currently running profile gateways within the container.

Frequently Asked Questions about adame-s6-container-supervision

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

FAQPage Schema
How do I manage s6-overlay supervision trees for Docker containers?

s6-overlay supervision trees are managed by configuring static services and per-profile gateways within the Docker image. This skill handles service registration and main-wrapper.sh execution logic to maintain reliable container behavior.

Why do my profile gateway services fail to persist after a Docker container restart?

Profile gateway persistence fails when boot reconciliation is missing. The skill automatically restores gateway states and permissions on container startup using s6-overlay v3.2.3.0 supervision logic.

What is the main-wrapper.sh pattern in s6-overlay architecture?

The main-wrapper.sh pattern is an architectural entry point that safely extends container behavior without breaking the s6 supervision tree. It ensures proper execution logic for static service registration and gateway management.

Do I need direct access to s6-overlay binary paths to debug container supervision?

Direct access to the container environment and s6-overlay binary paths is required to perform service status checks and configuration updates. This access enables debugging of per-profile gateway services and supervision trees.

Can I inspect the status of running profile gateways inside a Docker container?

Running profile gateways can be inspected by querying the s6-overlay supervision tree. The skill facilitates status checks against the container environment to verify static service registration and gateway execution logic.

What are the limitations of extending an s6-overlay supervision tree in Docker?

Extending the supervision tree risks breaking container behavior if the main-wrapper.sh pattern is ignored. Safe extension requires understanding s6-overlay v3.2.3.0 architecture and maintaining proper static service registration.