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.
In this repository62 other files it gives its agents.
- examples/recipes/partners/hpe/retail-assistant/docker-compose/scripts/identity/AGENTS.mdAGENTS.md
- examples/recipes/partners/hpe/retail-assistant/helm/files/identity/AGENTS.mdAGENTS.md
- examples/recipes/partners/tavily/watchtower/prompts/AGENTS.mdAGENTS.md
- nemoclaw-community-contributor-examplesSkill
- nemoclaw-community-maintainer-policiesSkill
- coach-nemoclaw-hermesSkill
- coordinate-nemoclaw-blenderSkill
- blender-host-sandbox-boundarySkill
- blender-python-api-verificationSkill
- ovphysx-host-runtime-boundarySkill
- axe-a11ySkill
- deep-researchSkill
- cross-source-gap-analysisSkill
- github-readonly-liveSkill
- nemoclaw-autohealSkill
- nemoclaw-nvteamSkill
- outlook-email-searchSkill
- slack-channel-finderSkill
- slack-channel-summarizerSkill
- source-etl-querySkill
- module-1Skill
- module-2Skill
- module-3Skill
- module-4Skill
- module-5Skill
- module-6Skill
- module-7Skill
- setup-workshop-nemoclaw-operatorSkill
- setup-workshop-nemoclawSkill
- workshopSkill
- cross-source-gap-analysisSkill
- github-readonly-liveSkill
- gitlab-readonly-liveSkill
- nemoclaw-autohealSkill
- nemoclaw-nvteamSkill
- outlook-email-searchSkill
- public-web-searchSkill
- slack-channel-finderSkill
- slack-channel-summarizerSkill
- source-etl-querySkill
- openshift-llm-deploySkill
- inbound-judgingSkill
- memory-consolidationSkill
- memory-repairSkill
- memory-writingSkill
- obligation-reviewSkill
- preference-updateSkill
- nv-tech-assistantSkill
- payment-ops-playbookSkill
- payment-screeningSkill
- rail-boundary-testSkill
- release-packetSkill
- pr-reviewSkill
- pr-test-case-assistantSkill
- vss-videoSkill
- nemoclaw-hermes-swarmSkill
- blackwall-payment-gateSkill
- retail-apiSkill
- retail-apiSkill
- watchtowerSkill
- The first 60 shown.
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
- Very specific: line 11
Prefer GET discovery, status, events, and logs.
- Very specific: line 12
Never send DELETE or request deletion through another workload.
- Very specific: line 13
If asked to delete, refuse and provide the exact resource identity plus a human-reviewable kubectl delete ...
- Very specific: line 14
Treat broad-no-delete as dangerous: create/update/patch can still cause outages or privilege escalation.
≈ “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
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.
- Inspect current state before proposing any mutation.
- Prefer
GETdiscovery, status, events, and logs. In safe mode, mutate only the/scalesubresource of a namespaced Deployment or StatefulSet; full workload patches are forbidden. - Never send
DELETEor request deletion through another workload. The proxy rejects DELETE and the service account has no delete verbs. - 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. - Treat
broad-no-deleteas 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.
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.

