Files

64 lines
2.4 KiB
Markdown

---
name: athena-operator
description: Understand, operate and extend the Athena AI host.
license: MIT
metadata:
hermes:
version: 2.0.0
author: Michael Roll
platforms: [linux]
tags: [athena, docker, mcp, models, backup]
---
# Athena Operator
Use this skill for work on Athena itself: Docker, MCPs, models, profiles,
Hermes, OpenWebUI, TTS, STT, image generation, Git and backups.
## Start
1. Call `athena_operator_inspect` with `subject=guide`; it returns the current
`ATHENA.md` as the architectural truth.
2. Inspect the affected live area only if needed.
3. Search for the concrete source file, then read only the required lines.
Do not rediscover the complete platform for every task. Do not read entire
large files when a bounded section is enough. Do not guess file paths.
## Change
When the user has clearly requested a change, use `athena_operator_change` to
apply the smallest durable change. The operator owns the Git worktree and
deployment access; do not clone another repository or request another SSH key.
Afterwards run focused checks, verify the affected service, commit and push.
The scheduled Docker-data backup is automatic. After storage-affecting work,
run one manual backup and verify its archive instead of building a special
recovery kit.
For a new MCP, normally change only its server code, Dockerfile, MCP Compose
service, env example, client registration and a focused test. Reuse an existing
backend instead of installing a duplicate service.
## Tool discipline
- One failed path may be corrected once. Repeated `file not found`, permission
or circuit-breaker responses mean stop and report the exact blocker.
- Keep search and terminal output bounded.
- Prefer specialist MCPs for Home Assistant, Unraid, ARR, Navidrome and other
external systems.
- A healthy container is not proof; perform one bounded functional check.
- Never claim a write, deploy, commit, push or backup succeeded without its
actual result.
## Remote-host boundary
Never shut down or reboot Athena and never change its SSH, LAN, WireGuard,
firewall, boot, kernel, partition or mount configuration unless the user gives
a separate explicit current instruction. Do not restart Router, Qwen, Hermes
or the whole stack merely to deploy one component.
Temporary helpers belong under `/tmp` or in an ephemeral container. Permanent
software belongs in the Git-managed stack. Secrets stay under `/etc/mike-ai`
and must not be committed or printed.