Automated summary
Reviews Kubernetes manifests, analyzes rollout safety, and diagnoses cluster workload issues with a production-safety focus.
Strengths
- Favors the smallest defensible change that restores reliability while keeping rollback options clear.
- Spans rollout strategy, probes and resources, service discovery, network policy, config/secret delivery, RBAC, storage, and observability.
- Explicitly separates confirmed facts from assumptions before proposing mitigation.
- Requires validation of the normal path, a failure path, and a recovery or rollback path.
Limitations
- Runs in a read-only sandbox: it cannot apply changes or run live cluster experiments.
- Quality depends on user-supplied manifests, logs, and cluster context; it has no direct telemetry access.
- Does not cover general application development or non-Kubernetes infrastructure provisioning.
Use when reviewing Kubernetes manifests, planning a safer rollout, or debugging pod, service, RBAC, or storage issues in a cluster.
Avoid for application code development, non-Kubernetes cloud provisioning, or when you need automated manifest application rather than read-only analysis.
Security analysis
SafeThis skill is purely advisory guidance for Kubernetes manifest review and rollout safety. It declares no tools and a read-only sandbox mode, and its instructions contain no destructive commands, network calls, credential handling, obfuscated payloads, or attempts to bypass safety controls. There is no meaningful execution risk.
No concerns found
How this analysis is madeExamples
Review this Deployment manifest for rollout safety. Check the update strategy, readiness/liveness/startup probes, resource requests and limits, and rollback behavior. Point out the smallest changes needed before production.Our pods started CrashLoopBackOff after a rollout. Here are the Deployment manifest, recent pod events, and container logs. Identify likely causes and the safest next diagnostic steps without widening the blast radius.Audit the RBAC in this namespace for least privilege. I'm providing the Role, RoleBinding, ServiceAccount, and workload manifests. Flag excessive permissions and propose minimal scoped changes that preserve the workload's required access.triggers:
- "kuuernetes specialist" name: kubernetes-specialist description: "Use when a task needs Kubernetes manifest review, rollout safety analysis, or cluster workload debugging." compatibility: opencode metadata: model: gpt-5.4 model_reasoning_effort: high sandbox_mode: read-only
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:
- Map the affected operational path (control plane, data plane, and dependency edges).
- Distinguish confirmed facts from assumptions before proposing mitigation or redesign.
- Implement or recommend the smallest coherent action that improves safety without widening blast radius.
- 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
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/kubernetes-specialist-mrx3xz7m/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/kubernetes-specialist-mrx3xz7m' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/kubernetes-specialist-mrx3xz7m/download' --output '.skill-downloads/kubernetes-specialist-mrx3xz7m/SKILL.md.part' && mv '.skill-downloads/kubernetes-specialist-mrx3xz7m/SKILL.md.part' '.skill-downloads/kubernetes-specialist-mrx3xz7m/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Environment declared by the author: opencode
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/kubernetes-specialist-mrx3xz7m'openskills read 'kubernetes-specialist-mrx3xz7m'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/kubernetes-specialist-mrx3xz7m/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
Configure a Chat Channel with SecretRefs
DevOps
Set up chat channels using non-interactive commands, with secrets only as SecretRefs. Covers gather, mutate, repair, and prove steps for reliable delivery.
Investigate ClickHouse CI Failures
DevOps
Investigate a ClickHouse CI failure end-to-end from a PR or S3 report URL. Fetches failed tests, classifies flaky vs real regression, and checks for existing issues/fixes.
Ansible PR Review
DevOps
Reviews an Ansible PR following the project's standardized process, including changelog checks, test coverage validation, and feedback tracking.