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

netbird

Skill4 starsChanged 5 months agoMITView on GitHub

Use when working with NetBird — route to the correct sub-skill based on what you need: client CLI, Terraform provider, or the Kubernetes operator.

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 37

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

NetBird — Skill Router

Latest client: v0.76.x (verified against local binary)
Latest Terraform provider: v0.0.9 (netbirdio/netbird)
Latest operator chart: v0.8.0 (ghcr.io/netbirdio/helm-charts/netbird-operator)
Latest server chart: v1.0.x (helmforge/netbird — repo.helmforge.dev)

Overview

NetBird is an open-source, WireGuard-based zero-trust mesh VPN. Peers connect peer-to-peer (with ICE/STUN NAT traversal and a relay fallback) into an encrypted overlay network. A central Management service holds network state, distributes peer keys, and enforces access policies. Four surfaces for working with it:

  • Server (control plane) — self-hosted netbird-server (management+signal+relay+STUN+embedded Dex IdP) + dashboard, deployed via the helmforge/netbird chart
  • CLI (netbird) — the client agent: connect/disconnect, status, networks, expose, ssh, k8s
  • Terraform provider (netbirdio/netbird) — declarative management of groups, peers, routes, networks, policies, setup keys, DNS, posture checks via the public API
  • Kubernetes operator (netbirdio/kubernetes-operator) — CRDs that expose in-cluster services and manage peers/routes/groups from inside K8s (consumes an existing control plane)

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
server, control plane, self-hosted, helmforge, netbird-server, management, signal, relay, STUN, dashboard, config.yaml, embedded IdP, Dex, deploy netbird, install netbirdDeploy/operate the NetBird control plane itself (management + signal + relay + dashboard)netbird-server
netbird up, netbird down, netbird status, netbird login, setup-key, setup key, peer, expose, reverse proxy, ssh, kubernetes, networks select, FQDN, overlay, WireGuard client, client installRun the netbird client on a machine (connect/register/troubleshoot a peer)netbird-cli
terraform, provider, netbird_group, netbird_peer, netbird_route, netbird_network, netbird_policy, netbird_setup_key, netbird_dns, netbird_posture_check, IaC, infra as code, plan, applyManage NetBird account resources as infrastructure codenetbird-terraform
operator, CRD, SetupKey, NetworkRouter, NetworkResource, NetworkEgress, SidecarProfile, ClusterProxy, Helm chart, in-cluster, expose service, kubeconfig, admission webhookRun NetBird inside Kubernetes / expose cluster services via CRDsnetbird-operator

Decision Tree

If routing is ambiguous:

  1. User is deploying/operating the control plane (chart, config.yaml, DB, IdP, gRPC routing) → netbird-server
  2. User is running client commands (up, status, networks, expose) → netbird-cli
  3. User is writing Terraform (.tf files, netbird_* resources) → netbird-terraform
  4. User is writing Kubernetes manifests (CRDs, Helm) → netbird-operator
  5. Combination? → Load the one matching the primary action. Common pairs: netbird-server deploys the API → netbird-terraform manages it (management_url at the in-cluster API) → netbird-cli registers peers with setup keys; the netbird-operator connects to the server via managementURL + PAT.

When NOT to load this router

  • User is working on Tailscale — that's a different mesh VPN (tailscale skill)
  • User asks about WireGuard config syntax — NetBird manages WireGuard automatically; raw WireGuard belongs in a general networking skill
  • User is setting up netbird on Talos nodes — combine netbird-cli (agent install) with tailscale-talos-style machine config knowledge, but the mesh itself is NetBird
  • 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.