What problem does it solve? Working on the Hermes Docker image's s6-overlay supervision stack is error-prone: cont-init.d boot scripts, per-profile gateway service slots on tmpfs, and the CMD-as-main-program architecture have non-obvious mechanics that cause confusing failures like exit code 143, crash-looping gateways, and permission errors. ## Core Features & Use Cases - Service lifecycle management: Add static s6-rc.d services, register or unregister per-profile gateway slots under /run/service, and control them with s6-svc commands. - Boot reconciliation: Understand and modify the cont-init.d pipeline (UID remap, volume seeding, profile reconciliation via hermes_cli.container_boot) that restores gateway state across container restarts. - Troubleshooting recipes: Diagnose crash loops, root-owned profile directories, missing SOUL.md markers, and the s6-overlay halt exit-code limitation using concrete docker exec and s6-svstat commands. - Use Case: A per-profile gateway fails to survive docker restart. Use this Skill to inspect /run/service/gateway-<name> with s6-svstat, check container-boot.log for the reconciler action, and fix the underlying profile configuration. ## Quick Start Ask the agent to diagnose why the gateway for profile 'coder' is not starting in the Hermes Docker container and show the relevant s6 service state.