System-Manager

Generate a structured SESSION_BRIEFING.md for AutomationOne ESP32 hardware test sessions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The System-Manager skill eliminates ambiguity and startup friction for AutomationOne hardware test sessions by producing a single, structured SESSION_BRIEFING.md that the Technical Manager can use to orchestrate agents, verify infrastructure status, and run reproducible tests.

Core Features & Use Cases

  • Automatic Session Detection: Recognizes trigger phrases and session starts to begin planning.
  • Read-only System Analysis: Gathers git status, server and MQTT checks, recent reports, and firmware metadata without making changes.
  • Agent Coordination & Templates: Produces a complete briefing with agent sequence, test scenarios, success criteria, risks, and references for the Technical Manager to execute.
  • Use Case: Start a DS18B20 sensor test on a physical ESP32 and receive a step-by-step briefing, required prechecks, and agent commands for VS Code.

Quick Start

Start a hardware test session by saying "session gestartet" and provide the ESP32 setup, device ID, sensors, server status, and test goal to generate a SESSION_BRIEFING.md.

Frequently Asked Questions about System-Manager

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

FAQPage Schema
How do I generate a structured test plan for ESP32 hardware sessions?

An ESP32 test plan is produced by triggering a session and providing device details. The skill performs read-only repository and runtime analysis to output a structured SESSION_BRIEFING.md with agent sequences and success criteria.

What is session orchestration for MQTT-based hardware testing?

MQTT hardware testing session orchestration coordinates agent delegation and pre-test system checks. It verifies server and MQTT status, loads firmware metadata, and creates a reproducible workflow briefing for technical managers.

Can I use this skill to check ESP32 and MQTT server status before running tests?

Yes, you can check ESP32 and MQTT server status before running tests. The skill performs read-only system analysis to gather git status, server connectivity, MQTT checks, and firmware metadata without making changes to the environment.

How do I start a hardware test session and get a briefing for agent coordination?

Start a hardware test session by saying "session gestartet" and provide the ESP32 setup, device ID, sensors, server status, and test goal. This generates a structured briefing with required prechecks and agent commands for VS Code.

Does the session briefing generation modify my repository or runtime environment?

Session briefing generation does not modify your repository or runtime environment. It performs strictly read-only analysis of git status, recent reports, and server checks to produce a formatted briefing file for technical review.