agentsclimarketplace

Kubernetes basics

Skill planifest/planifest-framework/planifest-framework/external-skills/kubernetes-basics

Kubernetes fundamentals workflow for workload deployment, service discovery, and baseline cluster primitives. Use when teams need concrete namespace/workload/service/probe decisions before deployment; do not use for API contract design or requirement prioritization.From its SKILL.md

Install
npx -y skills add planifest/planifest-framework --skill kubernetes-basics

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.1 KB, 365 tokens by cl100k_base, as published. Nobody here has run it

Kubernetes Basics

Overview

Use this skill to define a deployable Kubernetes baseline that is reproducible and operationally verifiable.

Scope Boundaries

  • Use this skill when the task matches the trigger condition described in description.
  • Do not use this skill when the primary task falls outside this skill's domain.

Shared References

  • Service discovery and probe rules:
    • references/service-discovery-and-probe-rules.md

Templates And Assets

  • Baseline workload manifest:
    • assets/workload-baseline-template.yaml
  • Basics verification checklist:
    • assets/k8s-basics-checklist.md

Inputs To Gather

  • Target workloads and service exposure model.
  • Namespace and resource-boundary requirements.
  • Health signal requirements and dependency expectations.
  • Rollout and rollback expectations.

Deliverables

  • Baseline workload/service manifest set.
  • Probe and discovery policy aligned with runtime behavior.
  • Namespace/resource boundary decisions.
  • Deployment verification checklist and evidence.

Workflow

  1. Define workload/service baseline using assets/workload-baseline-template.yaml.
  2. Apply probe and discovery guidance from references/service-discovery-and-probe-rules.md.
  3. Align namespace/resource boundaries with ownership and blast radius.
  4. Validate deployment behavior via assets/k8s-basics-checklist.md.
  5. Publish residual risks and follow-up actions.

Quality Standard

  • Baseline manifests are declarative and reviewable.
  • Service routing and probe semantics are explicit.
  • Readiness reflects true traffic-safety conditions.
  • Rollback path is clear before production rollout.

Failure Conditions

  • Stop when baseline workloads cannot be deployed reliably on target cluster.
  • Stop when probes do not represent meaningful application health.
  • Escalate when namespace/resource boundaries remain ambiguous.

What ships with it: 1 file

11.3 KB alongside SKILL.md

Keep looking

Skills are one crate of 326,834. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.