omni-scale

Generate a deployment plan using soft guidelines with anchored outputs.

Bootstrap GitOps stack (ArgoCD, ESO, Longhorn) onto existing Talos cluster

Execute disaster recovery drill - destroy and recreate cluster from specs

Load context for a new agent session by analyzing codebase structure and README

Check Omni cluster and GitOps health status

Use this agent to review mothership-gitops manifests before committing. Validates ArgoCD Applications, Helm values, External Secrets, namespace labels, and Tailscale Ingress patterns. <example> Context: User added a new ArgoCD Application. user: "Review my new ArgoCD app before I commit" assistant: "I'll use the gitops-reviewer agent to validate sync waves, destination namespace, and source configuration." <commentary> New ArgoCD apps need sync wave ordering validation to ensure dependencies deploy first. </commentary> </example> <example> Context: User deployed a new service with a web UI. user: "Check if my Homarr deployment is configured correctly" assistant: "I'll use the gitops-reviewer agent to verify the deployment has Tailscale Ingress for UI access." <commentary> Web UIs must have Tailscale Ingress - cluster-internal-only UIs are not acceptable. </commentary> </example> <example> Context: User is about to commit GitOps changes. user: "Review my mothership-gitops changes" assistant: "I'll use the gitops-reviewer agent to validate all modified manifests against GitOps patterns." <commentary> Pre-commit review catches sync wave ordering issues, missing Ingresses, and ESO configuration problems. </commentary> </example>

Use this agent to review Omni-Scale infrastructure manifests before committing. Validates machine classes, cluster templates, provider configs, and spec files against known patterns and constraints. <example> Context: User modified a machine class and wants to verify it before committing. user: "Review my changes to machine-classes/matrix-worker-hotel.yaml" assistant: "I'll use the omni-reviewer agent to validate the machine class against schema requirements and known constraints." <commentary> Machine class changes should be validated for required fields, CEL selector syntax, and provider data schema before committing. </commentary> </example> <example> Context: User created a new cluster template. user: "Check this cluster template before I deploy it" assistant: "I'll use the omni-reviewer agent to validate the cluster template structure, machine class references, and CNI configuration." <commentary> Cluster templates need multi-doc structure validation, version format checks, and machine class reference verification. </commentary> </example> <example> Context: User is about to commit changes to Omni-Scale repo. user: "Review my Omni-Scale changes before I commit" assistant: "I'll use the omni-reviewer agent to validate all modified infrastructure manifests." <commentary> Pre-commit review catches issues like CEL reserved keywords, missing required fields, or spec inconsistencies. </commentary> </example>

This skill provides operational tooling and guidance for Omni Proxmox infrastructure. Use when the user asks to "check provider status", "restart provider", "view provider logs", "debug provider registration", "create a machine class", "configure Proxmox provider", "set up CEL storage selectors", "create a Talos cluster", or needs guidance on Omni + Proxmox infrastructure integration for Talos Kubernetes clusters.