agentleFS
Aidas-devAidas-dev/k8s-agent-skills/AGENTS.md

k8s-agent-skills

AGENTS.md4 starsChanged 5 months agoMITView on GitHub

Every skill in this repo is published to npm and consumed by agents of any user, on any cluster. Skills must work standalone for anyone, anywhere. Forbidden in skills: Genericize it: describe the pattern, keep the structure, strip the specifics. The reader's cluster is different — the skill must survive that. Before committing any skill, grep for: IP literals, tailnet 100.x ranges, node hostnames, cluster names, and URLs pointing at personal infrastructure. If any present — rewrite before committing.

The file

We split this AGENTS.md into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is 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.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every skill in this repo is published to npm and consumed by agents of any user, on any cluster.

    line 5
  2. Very specific:

    Before committing any skill, grep for: IP literals, tailnet 100.x ranges, node hostnames, cluster names, and URLs pointing at personal …

    line 29

≈ “Common” is an estimate: at least 1 in 5 of the 41,581 AGENTS.md 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
AGENTS.md

AGENTS.md — k8s-agent-skills

Skills Must Be User-Agnostic

Every skill in this repo is published to npm and consumed by agents of any user, on any cluster. Skills must work standalone for anyone, anywhere.

Never hardcode cluster-specific data

Forbidden in skills:

  • Node names, IPs, tailnet addresses, hostnames (controlplane-svt, 100.x.x.x, talos-cluster)
  • Cluster names, endpoints, API URLs, domain names
  • Secrets, tokens, certs, private keys
  • Node counts, hardware specs, disk layouts of a specific deployment
  • Provider account IDs, tenant IDs, region names specific to one infra

What to write instead

  • Placeholder patterns: <node-ip>, <cluster-name>, https://<endpoint>:6443
  • Generic role labels: cp1/cp2/cp3, controlplane/worker
  • "Source of truth" references when a real repo pattern is genuinely instructive — but abstract the specifics (e.g. "secrets come from the live cluster, stored gitignored" — not the actual JSON path of one deployment)

If a real-world example adds value

Genericize it: describe the pattern, keep the structure, strip the specifics. The reader's cluster is different — the skill must survive that.

Review gate

Before committing any skill, grep for: IP literals, tailnet 100.x ranges, node hostnames, cluster names, and URLs pointing at personal infrastructure. If any present — rewrite before committing.

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.