homeserver-infrastructure

Diagnose Docker containers, verify host volume mounts, and integrate Alexa cloud services on home servers.

Updated Jul 27, 2026
One-click install
npx skills add https://github.com/moistalgia/hermes-tools --skill homeserver-infrastructure-moistalgia
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: homeserver-infrastructure
Source: https://github.com/moistalgia/hermes-tools/tree/main/skills-from-hermes/homeserver-infrastructure/homeserver-infrastructure
Command: npx skills add https://github.com/moistalgia/hermes-tools --skill homeserver-infrastructure-moistalgia

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Running an AI agent on a personal media or compute server raises recurring infrastructure questions: which Docker containers are running, whether host directories are actually mounted into the agent's sandbox, and how to control cloud-only smart home platforms like Amazon Alexa or SmartLife that have no local CLI tools. ## Core Features & Use Cases - Docker Topology Diagnosis: Clarifies per-session container counts, runs docker ps and docker inspect when available, and falls back to asking the user to check on their host when the sandbox lacks Docker access. - Volume Mount Verification: Lists and inspects mounted directories (ls, df, mount) before suggesting new mounts, avoiding duplicate or conflicting volume configuration. - Cloud Service Integration: Provides a decision matrix comparing Home Assistant, MQTT bridge, Tuya local protocol, and the official Alexa Developer API, with a detailed reference guide for Alexa integration. - Use Case: A user asks why they see five containers in Docker Desktop and whether the agent can control their SmartLife blinds; the skill identifies the session containers, confirms the /sandbox mounts, and recommends a Home Assistant container with the Alexa Media Player integration. ## Quick Start Ask the agent to check which Docker containers are running on your server and whether your shared folders are mounted into its environment.

Frequently Asked Questions about homeserver-infrastructure

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

FAQPage Schema
How do I check which Docker containers my home server is running?▼

Run `docker ps --format "{{.ID}}\t{{.Names}}\t{{.Image}}"` on the host to list containers, and `docker inspect <container>` for volume and configuration details. Each agent session typically gets its own container, so the count matches active sessions plus your other services.

How to integrate Amazon Alexa devices with a local home server?▼

The recommended path is running Home Assistant in Docker with the Alexa Media Player integration, which syncs Echo and SmartLife devices and exposes a local REST API. Alternatives include an MQTT bridge script or the official Alexa Developer API, each with different maintenance trade-offs.

Why does 'docker: command not found' appear inside the agent environment?▼

This is an environment limitation, not proof that Docker is missing. Agent sessions run inside a sandboxed container that often lacks access to the host's Docker socket, so run diagnostics directly on the host machine instead.

How do I verify a host directory is mounted into a Docker container?▼

List the directory first with `ls -la`, then check `df /path` or `mount | grep <name>` to see whether the filesystem is an overlay or a backed volume. If the directory exists and is writable, it is likely already mounted from the host's compose file.

What are the limitations of MQTT bridge scripts for Alexa control?▼

MQTT bridges rely on Amazon's undocumented internal APIs, which change frequently and break bridge scripts. They also require ongoing OAuth token refresh handling, making them the highest-maintenance option compared to Home Assistant or the official API.