agentleFS
Sign inStart free
last9last9/mithai/skills/kubernetes/SKILL.md

kubernetes

Skill20 starsChanged 5 months agoApache-2.0View on GitHub

You can inspect Kubernetes clusters with safe, read-only kubectl operations. Use this skill when the user asks about pods, deployments, recent events, workload status, or container logs.

31 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use gitops, documentation-site and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • kcns008Skill

    gitops

    GitOps Agent (Flow) — manages ArgoCD applications, Helm charts, Kustomize overlays, deployment strategies (canary, blue-green, rolling), multi-cluster GitOps, and drift detection for Kubernetes and OpenShift clusters.

    Also in 4 projects that use this

  • KMaruthi2002Skill

    documentation-site

    Plan, build and maintain a documentation website for a product, API, library, platform or internal system: information architecture (tutorials, how-to guides, reference, explanation), choosing a static site generator or hosted docs platform, navigation and search, versioning for multiple releases, generated API reference, code samples that are tested and actually run, docs-as-code workflow with review, previews, link checking and CI, plus accessibility, internationalisation and analytics. Use when someone asks to create a docs site, developer portal, knowledge base, handbook site, migrate docs to a new generator, add versioning or search to docs, or fix docs that users cannot navigate or that have drifted from the product.

    Also in 3 projects that use this

  • SentrySkill

    datadog

    Query live Datadog telemetry (logs, metrics, traces, spans, monitors, incidents, dashboards, services, hosts) through Datadog's Pup CLI. Use when users ask to investigate production behavior in Datadog, including searching logs, checking monitor status, inspecting traces or spans, looking up incidents, finding services, or correlating metrics. Do not use it for Sentry issues, repository/source-code work, or ticketing.

    Also in 3 projects that use this

  • ihiteshguptaSkill

    terraform

    Expert in Infrastructure as Code with Terraform. Use for creating, managing, and versioning infrastructure across cloud providers.

    Also in 5 projects that use this

  • ddehartSkill

    process

    Process work sessions into the claude-code-plugins knowledge graph — preserves the session transcript, writes or links its chronicle entry as the session's synthesis, turns the transcript into observations, updates the patterns and decisions they support, folds in named plugins and skills, and proposes promotions to the personal commons. Also resolves-and-preserves an on-demand Claude Code docs URL when one comes up. Use when the user says "process this session", "run /process", names a session transcript or UUID, names a chronicle entry whose session should be processed, asks what's in the processing queue, or points at a Claude Code release-notes / docs page to capture.

    Also in 3 projects that use this

  • third-order-labsSkill

    project-scaffolding

    Templates, directory conventions, and document structure for long-form fiction projects. Contains the full template library — documents are created as the project needs them, not all at once.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 3 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 27 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when the user asks about pods, deployments, recent events, workload status, or container logs.

    line 3
  2. Distinctive:

    Only inspect resources. This skill does not create, update, restart, scale, or delete anything.

    line 8
  3. Very specific:

    Prefer get_pods before fetching logs so you know the exact pod and namespace.

    line 9
  4. Very specific:

    Use get_events when diagnosing Pending, CrashLoopBackOff, ImagePullBackOff, or scheduling issues.

    line 10
  5. Very specific:

    Use describe_resource when a concise object summary is not enough.

    line 11
  6. Distinctive:

    If kubectl returns an error, report it plainly and do not invent cluster state.

    line 13

“Common” is measured: kept by at least 6 in 10 of the 27 edited versions of this file we could read. “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

You can inspect Kubernetes clusters with safe, read-only kubectl operations.

Use this skill when the user asks about pods, deployments, recent events, workload status, or container logs.

Rules:

  • Only inspect resources. This skill does not create, update, restart, scale, or delete anything.
  • Prefer get_pods before fetching logs so you know the exact pod and namespace.
  • Use get_events when diagnosing Pending, CrashLoopBackOff, ImagePullBackOff, or scheduling issues.
  • Use describe_resource when a concise object summary is not enough.
  • Include namespace, pod names, phases, restart counts, and relevant event reasons in your answer.
  • If kubectl returns an error, report it plainly and do not invent cluster state.

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.

Check your setup, free