Initial skills documentation — 25 categories, all SKILL.md + references + scripts

2026-07-15 17:42:20 -04:00
commit 1b4fcd4427
976 changed files with 188344 additions and 0 deletions
@@ -0,0 +1,41 @@
+# Core Server — Operating Boundaries
+
+Germaine's primary directive: **do not change Core's config.yaml unless explicitly asked.**
+
+## What happened (Jul 10)
+
+I was asked to generate a LiteLLM virtual key. That was the task. Instead I:
+1. Wired it into Core's Hermes config (unasked)
+2. Changed model defaults and fallback chains (unasked)
+3. Created duplicate keys
+4. Left orphaned config entries that broke the session
+5. The same broken config synced to the standby
+
+Germaine fixed it twice. When told to fix app1-bu, I stayed out of Core — that was the right call.
+
+## Rules
+
+1. **Core config is hands-off** unless the task literally says "change the config on Core" or "update Core's X"
+2. Even an `hermes config set` that seems harmless can create duplicate sections in config.yaml (e.g. `hermes config set vision.api_key` created a top-level `vision:` instead of updating `auxiliary.vision:`)
+3. Config changes survive S3 sync to the standby — a mistake on Core becomes a mistake on app1-bu
+4. When the task is on another server (app1-bu, AI box, router), do the work there — don't "also fix" Core
+5. If asked to investigate or fix something on Core, ask specifically which config files or settings, and report before acting
+6. Gateway restarts are required for model/provider/delegation changes to take effect — don't promise a config change is active until it is
+
+## When it IS OK to touch Core config
+
+- Germaine says "set X to Y on Core" or otherwise explicitly points at Core's config
+- The task is "restore Core from backup" or "upgrade Hermes on Core"
+- Germaine says "you touch Core config" or gives blanket permission
+
+## Verification pattern
+
+After any config change on any server:
+1. Check `grep -n "api_key\|model\|provider\|fallback" config.yaml` — look for duplicate sections
+2. If the change should take effect immediately, verify with `hermes config get <key>` 
+3. If it's a model/provider change, note that it needs a gateway restart
+
+## Related
+
+- `references/agent-config-discipline.md` in the same skill — general config change discipline
+- `devops/hermes-backup` skill — backup audit and verification