Document Athena containers and expand Hermes operator skill

platform/hermes/skills/athena-operator/SKILL.md

@@ -1,44 +1,53 @@
 ---
 name: athena-operator
-description: Understand, operate and extend the Athena AI host.
+description: Operate and extend Mike's Athena AI host safely. Use for Athena models, profiles, Docker services, GPU allocation, inference modes, benchmarks, cleanup, deployment, backups, documentation, or when testing a new local AI model for Hermes.
 license: MIT
 metadata:
   hermes:
-    version: 2.0.0
+    version: 3.0.0
     author: Michael Roll
     platforms: [linux]
-    tags: [athena, docker, mcp, models, backup]
+    tags: [athena, docker, gpu, models, benchmark, cleanup, backup]
 ---
 
 # Athena Operator
 
-Use this skill for work on Athena itself: Docker, MCPs, models, profiles,
-Hermes, OpenWebUI, TTS, STT, image generation, Git and backups.
+Use this skill for work on Athena itself: Docker, models, profiles, Hermes
+integration, TTS, STT, image/audio/music workers, 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.
+1. Call `athena_operator_inspect` with `subject=guide`.
+2. Choose and read the matching reference before acting:
+   - architecture, containers or modes: `references/architecture-and-modes.md`
+   - a model download, profile or A/B test: `references/model-evaluation.md`
+   - deployment, cleanup, documentation or publication:
+     `references/change-and-cleanup.md`
+3. Inspect only the affected live area with `overview`, `containers`, `models`,
+   `jobs` or `git_status`.
+4. Search for the exact source path before reading or editing it.
 
 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.
+When the user clearly requests 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.
+Afterwards run focused checks, verify the affected service functionally, update
+the affected documentation, 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.
+For every model candidate, preserve the currently working profile until the
+candidate is downloaded and ready. Compare like with like, record the exact
+artifact and result in `docs/TESTED_MODELS.md`, then either promote it or remove
+its weights and test-only runtime. Never silently lower a standard profile
+below Q4; Q3 is allowed only after a documented comparison shows negligible
+quality loss for the intended work.
 
 ## Tool discipline
 
@@ -48,6 +57,8 @@ backend instead of installing a duplicate service.
 - Prefer specialist MCPs for Home Assistant, Unraid, ARR, Navidrome and other
   external systems.
 - A healthy container is not proof; perform one bounded functional check.
+- `Created` or cleanly stopped model workers are normal on-demand services, not
+  proof of garbage.
 - Never claim a write, deploy, commit, push or backup succeeded without its
   actual result.