agentleFS
Aidas-devAidas-dev/k8s-agent-skills/skills/talos/SKILL.md

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.

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
  1. Distinctive:

    If routing is ambiguous:

    line 30

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 keywordsUser wants to...Skill to load
talosctl, upgrade, upgrade-k8s, bootstrap, kubeconfig, reboot, reset, rollback, etcd, service, logs, dmesg, dashboard, health, diagnostics, troubleshoot, CLIRun talosctl commands against a clustertalosctl
machine config, config, gen config, apply-config, patch, patching, secrets.yaml, network config, install disk, multi-document, v1alpha1, YAML config, LUKS, KubeSpan, disk encryptionWrite or modify machine config YAMLtalosconfig
terraform, provider, siderolabs/talos, talos_machine, machine_secrets, machine_configuration, cluster, IaC, infra as code, plan, applyManage Talos as infrastructure codetalos-terraform
tuppr, TalosUpgrade, KubernetesUpgrade, automated upgrade, orchestrated upgrade, GitOps upgrade, upgrade controller, maintenance windowAutomate Talos/K8s upgrades via Kubernetes controllertuppr

Decision Tree

If routing is ambiguous:

  1. User is running commands (upgrade, bootstrap, diagnostics) → talosctl
  2. User is writing YAML (config documents, patches) → talosconfig
  3. User is writing Terraform (.tf files, talos_* resources) → talos-terraform
  4. User wants automated/GitOps upgrades (CRs, controller, TalosUpgrade/KubernetesUpgrade) → tuppr
  5. Combination? → Load the one matching the primary action; config often flows into CLI usage, so talosconfig → talosctl is 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-terraform skill covers the Talos-side resources
  • User is working on Tailscale on Talos nodes → load tailscale-talos instead
  • User just needs a quick version/overview → the Overview above is sufficient

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.