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

skills/devops/infrastructure-automation/references/service-dependency-diagram.md

@@ -0,0 +1,27 @@
+# Service Dependency Diagram
+
+## Location
+
+`/root/portal-mockup/dependency-diagram.html`
+
+## Access
+
+Published at `https://vaultwarden.tailc2f3b0.ts.net/portal/dependency-diagram.html`
+
+## Governance
+
+This diagram is the canonical visual reference for how all ITPP services connect. Before making structural changes (adding/removing servers, changing providers, deploying new services), consult the diagram to understand blast radius and dependencies. After any infrastructure change, update the diagram so it reflects the current state.
+
+The diagram is a single self-contained HTML file (dark theme, JetBrains Mono, inline SVG). It has 7 layers: Users, Messaging/Providers, Core Services, Mail, Storage, Standby/External, and Config/Secrets. Three info cards at the bottom: Core Services, External Dependencies, Single Points of Failure.
+
+## When to Update
+
+- New server deployed or decommissioned
+- Provider change (new backup target, new LLM provider)
+- New email account or service added to monitoring
+- Cron jobs added/removed that change the service landscape
+- New integration added to the stack
+
+## Diagram Format
+
+The user expects a dark-themed SVG with color-coded component types (cyan=Hermes, emerald=system, violet=email, amber=external, rose=security). Grid background, labeled connections, and a legend at bottom-right. Info cards below the SVG with summary stats.