system-control

Manage and verify the AutomationOne Docker stack lifecycle and health.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Auto-one-Family/Automation-One --skill system-control
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: system-control
Source: https://github.com/Auto-one-Family/Automation-One/tree/main/.claude/skills/system-control
Command: npx skills add https://github.com/Auto-one-Family/Automation-One --skill system-control

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a single, operationally focused interface to manage, verify and diagnose the AutomationOne Docker-based IoT system so operators can reliably start/stop the stack, run health checks, observe MQTT traffic, access logs, and prepare hardware test sessions without hunting through docs.

Core Features & Use Cases

  • Docker-Stack Lifecycle: start, stop, rebuild and clean including production, development and test overlays.
  • Health & Monitoring: liveness/readiness probes, container healthchecks, Prometheus/Grafana monitoring guidance and targeted verification commands.
  • Session & Debug Management: orchestrated debug sessions with automated log archiving, STATUS generation, MQTT captures and session scripts for hardware tests and e2e validation.
  • Operational Playbooks: CI analysis, safety gates for destructive actions (make clean, db-restore), agent recommendation strategy and briefing workflow for Technical Managers.
  • Use Case Example: Prepare a hardware test session by starting the stack, initiating MQTT capture, creating a SESSION_BRIEFING.md, and instructing debug agents to collect ESP serial and server logs.

Quick Start

Start a debug session named test, bring up the Docker stack, and run a full health and MQTT check by running make up followed by make status and make health.

Frequently Asked Questions about system-control

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

FAQPage Schema
How do I manage the lifecycle of a Docker-based IoT stack?

Managing a Docker-based IoT stack lifecycle involves executing make and docker-compose targets to start, stop, rebuild, and clean containers across production, development, and test overlays. This ensures reliable stack operations and configuration management.

How do I run health checks and monitor MQTT traffic for Docker containers?

To run health checks and monitor MQTT traffic, execute targeted verification commands and liveness probes against container health endpoints. This captures MQTT traffic data and verifies overall Docker container system readiness.

What is the best way to prepare an ESP32 hardware test session?

Preparing an ESP32 hardware test session requires starting the Docker stack, initiating MQTT capture, and generating a session briefing document. This orchestrates debug agents to collect ESP serial and server logs for validation.

Can I use session scripts to access Docker container logs for debugging?

Yes, you can use session scripts to access Docker container logs for debugging. These scripts orchestrate debug sessions with automated log archiving and status generation to provide accurate diagnostics for system analysis.

When should I apply safety gates to destructive Docker operations like make clean?

You should apply safety gates to destructive Docker operations like make clean or database restores to prevent accidental data loss. These operational playbooks ensure destructive actions are verified before execution.