agentleFS
ByronScottJonesByronScottJones/Agents/skills/validate-and-deploy-kubernetes/SKILL.md

validate-and-deploy-kubernetes

Skill7 starsChanged 2 months agoMITView on GitHub

Use when validating, diffing, applying, rolling back, or health-checking Kubernetes manifests. Defaults to read-only validation and dry-run behavior; cluster mutations require explicit confirmation.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    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:

    Check labels, requests and limits, probes, security contexts, service accounts, secrets, network exposure, and policy rules.

    line 26
  2. Distinctive:

    Run client-side and server-side dry runs when available.

    line 28
  3. Distinctive:

    Never apply to a cluster without naming the context and namespace.

    line 36
  4. Distinctive:

    Never delete resources implicitly.

    line 37
  5. Distinctive:

    Never print secret values.

    line 38
  6. Distinctive:

    Stop on failed rollout or degraded health unless rollback was explicitly enabled.

    line 39

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Validate and Deploy Kubernetes

Implement kubernetes.md as a manifest and rollout workflow.

Parameters

  • manifestPath: default k8s/ or manifests/.
  • clusterContext: required for apply and rollback; current kubectl context may be used only for read-only validation and diff operations.
  • namespace: default default.
  • mode: validate, diff, apply, or rollback; default validate.
  • checkPolicy, checkSecurity, checkResources: default true.
  • waitForHealth: default true for apply.
  • rolloutTimeout: default 10m.
  • format: summary or json; default summary.

Workflow

  1. Parse YAML and validate Kubernetes schemas and kinds.
  2. Check labels, requests and limits, probes, security contexts, service accounts, secrets, network exposure, and policy rules.
  3. Run client-side and server-side dry runs when available.
  4. Produce a diff before apply.
  5. For apply, require an explicit context and confirmation, apply the reviewed manifests, wait for rollout, and run health checks.
  6. For rollback, identify the target revision, confirm scope, roll back, and verify health.

Safety

  • Never apply to a cluster without naming the context and namespace.
  • Never delete resources implicitly.
  • Never print secret values.
  • Stop on failed rollout or degraded health unless rollback was explicitly enabled.

Output

Return cluster target, resources checked, policy findings, diff summary, rollout status, health checks, rollback status, and remaining risks.

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.