talos
Skill4 starsChanged 5 months agoMITView on GitHub
Use when working with Talos Linux — route to the correct sub-skill based on what you need: talosctl CLI operations, machine configuration, or the Terraform provider.
In this repository74 other files it gives its agents.
- AGENTS.mdAGENTS.md
- atlasSkill
- cert-managerSkill
- cilium-gatewaySkill
- cilium-networkSkill
- cnpgSkill
- dragonflySkill
- external-dnsSkill
- external-secretsSkill
- flaggerSkill
- fluxSkill
- gitea-apiSkill
- gitea-registrySkill
- gitea-runnerSkill
- giteaSkill
- gitea-teaSkill
- gitea-webhooksSkill
- harbor-apiSkill
- harbor-helmSkill
- harborSkill
- harbor-terraformSkill
- helm-chartSkill
- helm-opsSkill
- helmSkill
- higress-helmSkill
- higress-operatorSkill
- higressSkill
- kserve-helmSkill
- kserve-operatorSkill
- kserveSkill
- kubeflow-pipelinesSkill
- kubeflowSkill
- kubeflow-trainerSkill
- kubeflow-training-operatorSkill
- mariadb-helmSkill
- mariadb-operatorSkill
- mariadbSkill
- netbird-cliSkill
- netbird-operatorSkill
- netbird-serverSkill
- netbirdSkill
- netbird-terraformSkill
- nextcloud-apiSkill
- nextcloud-helmSkill
- nextcloudSkill
- nvidia-device-pluginSkill
- rook-ceph-operatorSkill
- rook-cephSkill
- rook-ceph-toolboxSkill
- sealed-secretsSkill
- stakater-reloaderSkill
- tailscaleSkill
- tailscale-talosSkill
- talosconfigSkill
- talosctlSkill
- talos-terraformSkill
- tekton-operatorSkill
- tekton-pacSkill
- tekton-pipelinesSkill
- tektonSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 30
If routing is ambiguous:
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Talos — Skill Router
Latest: v1.13.x (Linux 6.18, etcd 3.6.9, K8s 1.36)
API version: v1alpha1 (multi-document config format)
Overview
Talos is an immutable Kubernetes OS — no SSH, no shell, API-driven. All management via talosctl, machine config YAML, or the Terraform provider.
Which Sub-Skill?
Match the user's request against the trigger keywords below, then call skill(name="<matched-skill>") to load the sub-skill's full content.
Routing Table
| Trigger keywords | User wants to... | Skill to load |
| talosctl, upgrade, upgrade-k8s, bootstrap, kubeconfig, reboot, reset, rollback, etcd, service, logs, dmesg, dashboard, health, diagnostics, troubleshoot, CLI | Run talosctl commands against a cluster | talosctl |
| machine config, config, gen config, apply-config, patch, patching, secrets.yaml, network config, install disk, multi-document, v1alpha1, YAML config, LUKS, KubeSpan, disk encryption | Write or modify machine config YAML | talosconfig |
| terraform, provider, siderolabs/talos, talos_machine, machine_secrets, machine_configuration, cluster, IaC, infra as code, plan, apply | Manage Talos as infrastructure code | talos-terraform |
| tuppr, TalosUpgrade, KubernetesUpgrade, automated upgrade, orchestrated upgrade, GitOps upgrade, upgrade controller, maintenance window | Automate Talos/K8s upgrades via Kubernetes controller | tuppr |
Decision Tree
If routing is ambiguous:
- User is running commands (upgrade, bootstrap, diagnostics) →
talosctl - User is writing YAML (config documents, patches) →
talosconfig - User is writing Terraform (
.tffiles,talos_*resources) →talos-terraform - User wants automated/GitOps upgrades (CRs, controller,
TalosUpgrade/KubernetesUpgrade) →tuppr - Combination? → Load the one matching the primary action; config often flows into CLI usage, so
talosconfig→talosctlis a common pair
When NOT to load this router
- User question is about a specific OS-level concern (kernel, hardware, GPU) → check if a hardware/GPU skill applies first
- User needs cluster provisioning on a specific cloud (Hetzner, Proxmox, AWS) → that's the cloud provider's concern; the
talos-terraformskill covers the Talos-side resources - User is working on Tailscale on Talos nodes → load
tailscale-talosinstead - User just needs a quick version/overview → the Overview above is sufficient
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

