What problem does it solve? Maintaining a browsable catalog of container images and turning a selected app into validated, deployable Kubernetes manifests requires manual translation of registry metadata, volume/port mappings, and GitOps PR workflows. This Skill codifies that entire pipeline for the lab's transparent registry catalog. ## Core Features & Use Cases - Catalog index generation: Poll provider APIs (linuxserver.io, NVIDIA NGC) to regenerate docs/data/catalog/<provider>.json following the catalog index schema. - Install-time translation: Convert upstream LSIO config (env vars, volumes, ports, security capabilities) into Kubernetes Deployments, PVCs, and ClusterIP Services with lab conventions like local-path storage. - Offline validation and GitOps PR flow: Validate rendered manifests against resource-quota and registry-allowlist rules, then commit to a branch and open a PR via the GitHub REST API. - Use Case: Run argo submit --from workflowtemplate/catalog-install-lsio -p app=jellyfin -p mode=gitops to render, validate, and open a PR that ArgoCD deploys into a catalog-jellyfin namespace. ## Quick Start Ask the assistant to render and validate a catalog app install by running the LSIO install translator for jellyfin and then submitting the gitops-mode Argo workflow.