What problem does it solve? Adding a service to a k3s homelab involves many easy-to-miss steps: the Ansible role skeleton, the inventory entry, deploy ordering, secrets, and the GitOps auto-deploy declaration. This Skill walks through each step so a new workload actually deploys instead of silently doing nothing. ## Core Features & Use Cases - Role scaffolding guidance: Copy the right sibling role (freshrss for plain web apps, sonarr for media-volume apps) and follow enforced conventions like descriptive volume names and manifest-only templates directories. - Automatic deploy ordering: Explains how the k8s play derives Traefik and Authelia dependency edges from templates, and when to declare explicit depends_on entries. - Secrets and GitOps handling: Covers SOPS-encrypted secrets, stale Secret key cleanup, and the k8s_autodeploy declaration with the denylist re-render step for opted-out roles. - Use Case: You want to add a new self-hosted app to the cluster. Follow the Skill to create the role, register it in containers_list, add secrets, deploy with a tag, and verify the service behind Authelia rather than just the pod. ## Quick Start Use the new-k8s-service skill to add a service called 'linkding' to the k3s cluster and walk me through the role, inventory entry, secrets, and first deploy.
