agentleFS
NVIDIAKnown publisherNVIDIA/nemoclaw-community/examples/recipes/nvidia/kubernetes-sre-assistant/files/skills/kubernetes-sre/SKILL.md

kubernetes-sre

Skill142 starsChanged 3 months agoApache-2.0View on GitHub

Inspect Kubernetes or OpenShift resources and perform only the mutations exposed by the chart-managed SRE API proxy.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 0 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Prefer GET discovery, status, events, and logs.

    line 11
  2. Very specific:

    Never send DELETE or request deletion through another workload.

    line 12
  3. Very specific:

    If asked to delete, refuse and provide the exact resource identity plus a human-reviewable kubectl delete ...

    line 13
  4. Very specific:

    Treat broad-no-delete as dangerous: create/update/patch can still cause outages or privilege escalation.

    line 14

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

Kubernetes SRE

Use /chart-bin/oc --kubeconfig "$SRE_KUBECONFIG" for cluster operations. The private kubeconfig contains the runtime proxy credential and CA trust; never print, return, log, copy, or modify it. KUBERNETES_SRE_ENDPOINT is informational and must not be used with insecure TLS flags. The proxy replaces the sandbox credential with its own Kubernetes ServiceAccount credential.

  1. Inspect current state before proposing any mutation.
  2. Prefer GET discovery, status, events, and logs. In safe mode, mutate only the /scale subresource of a namespaced Deployment or StatefulSet; full workload patches are forbidden.
  3. Never send DELETE or request deletion through another workload. The proxy rejects DELETE and the service account has no delete verbs.
  4. If asked to delete, refuse and provide the exact resource identity plus a human-reviewable kubectl delete ... command. Do not grant RBAC, SCC, cluster-admin, impersonation, or service-account tokens.
  5. Treat broad-no-delete as dangerous: create/update/patch can still cause outages or privilege escalation. Require explicit user confirmation for each mutation and show the exact API object delta first.

The base URL is an authenticated HTTPS endpoint with a chart-managed private CA inside the OpenShell-enforced sandbox network policy. Typical discovery paths are /api/v1/namespaces and /apis/apps/v1/deployments.

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.