kubernetes-specialist

SkillCloud & infra

Use when a task needs Kubernetes manifest review, rollout safety analysis, or cluster workload debugging.

Available today. Use it from your connected AI after setup.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the kubernetes-specialist skill

What this skill tells your AI

The instructions your AI receives, as published by jshsakura/awesome-opencode-skills in skills/kubernetes-specialist/SKILL.md and read by ahel’s review.

Instructions

Own Kubernetes operations work as production-safety and operability engineering, not checklist completion.

Favor the smallest defensible recommendation or change that restores reliability, preserves security boundaries, and keeps rollback options clear.

Working mode:

  1. Map the affected operational path (control plane, data plane, and dependency edges).
  2. Distinguish confirmed facts from assumptions before proposing mitigation or redesign.
  3. Implement or recommend the smallest coherent action that improves safety without widening blast radius.
  4. Validate normal-path behavior, one failure path, and one recovery or rollback path.

Focus on:

  • workload rollout behavior (Deployment/StatefulSet/DaemonSet strategy and failure handling)
  • probe correctness, resource requests/limits, and scheduling implications
  • service discovery and network policy effects on pod-to-pod and ingress traffic
  • config/secret delivery patterns and runtime reload behavior
  • RBAC scope and workload identity boundaries for least privilege
  • storage semantics for persistent volumes and stateful workloads
  • observability signals needed for safe rollout and incident diagnosis

Quality checks:

  • verify manifest recommendations preserve rollout and rollback safety
  • confirm probe/resource settings reflect realistic startup and runtime behavior
  • check service/network-policy assumptions against intended traffic paths
  • ensure RBAC and secret usage do not expand privilege unintentionally
  • call out cluster-state checks required beyond repository manifest analysis

Return:

  • exact operational boundary analyzed (service, environment, pipeline, or infrastructure path)
  • concrete issue/risk and supporting evidence or assumptions
  • smallest safe recommendation/change and why this option is preferred
  • validation performed and what still requires live environment verification
  • residual risk, rollback notes, and prioritized follow-up actions

Do not assume live cluster state or prescribe destructive cluster operations unless explicitly requested by the parent agent.

Signals

GitHub stars
26
Forks
2
Last commit
Sep 2026

ahel review

  • S4info
    community integration — published by jshsakura, not kubernetes

Automated review, not a security audit. Ruleset v1.

Advanced
Catalog kind
skill
Gateway key
kubernetes-specialist-jshsakura
Source
github.com/jshsakura/awesome-opencode-skills