Kubernetes

Skill notque/vexjoy-agent/skills/infrastructure/kubernetes

VexJoy AI Agent with Intelligent Routing - /do routes plain-English requests to the right specialist agent and gates the work with reviews, tests, and a learning loop.

Install

npx -y skills add notque/vexjoy-agent --skill kubernetes

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

What its author says it does

Copied from the file, not written here

Kubernetes operations: debugging, security, RBAC, and infrastructure tooling.

SKILL.md

4.2 KB, as published. Nobody here has run it

Kubernetes Skill

Kubernetes debugging, security hardening, and infrastructure tooling. Covers pod triage, RBAC, network policies, and cobaltcore hypervisor components.

Reference Loading Table

Signal	Reference	Size
CrashLoopBackOff, OOMKilled, config error, health check, liveness probe, ImagePullBackOff, Pending, FailedScheduling	`references/crash-diagnosis.md`	~140 lines
service resolution, DNS, CoreDNS, port-forward, NetworkPolicy ingress/egress	`references/network-debugging.md`	~50 lines
CPU throttling, memory limit, OOMKill, ephemeral storage, DiskPressure, debug container	`references/resource-debugging.md`	~100 lines
RBAC, Role, RoleBinding, ClusterRole, ServiceAccount, least-privilege	`references/rbac-patterns.md`	~60 lines
PodSecurity, SecurityContext, runAsNonRoot, readOnlyRootFilesystem, restricted, baseline	`references/pod-security.md`	~90 lines
NetworkPolicy, default-deny, allow-list, namespace isolation	`references/network-policies.md`	~70 lines
cosign, Kyverno, OPA, admission controller, Sealed Secrets, External Secrets	`references/supply-chain.md`	~120 lines
kvm-exporter, metrics, prometheus, libvirt, hypervisor, collector, scrape, steal time, NUMA, cgroups, cloud hypervisor	`references/cobalt-kvm-exporter.md`	~800 lines
cobaltcore concurrency, goroutine, semaphore, TryLock	`references/cobalt-concurrency-patterns.md`	~200 lines
cobaltcore testing, mock, moq, Kind cluster	`references/cobalt-testing-patterns.md`	~200 lines
kubernetes debugging process, triage flow, diagnosis routing	`references/kubernetes-debugging.md`	~50 lines
kubernetes security process, RBAC + pod security + network hardening	`references/kubernetes-security.md`	~50 lines
cobaltcore overview, KVM exporter architecture, component identification	`references/cobalt-core.md`	~50 lines

Loading rule. Read the references whose signals match the task before responding.

Phase 1: TRIAGE

Determine which Kubernetes domain the request targets:

Domain	Load references	Action
Pod failure, CrashLoop, OOM	crash-diagnosis, resource-debugging	Triage flow
Network, DNS, service resolution	network-debugging, network-policies	Connectivity diagnosis
RBAC, permissions, roles	rbac-patterns	Access control
Pod hardening, container security	pod-security	Security posture
Image signing, secrets, admission	supply-chain	Supply chain
Cobaltcore / KVM exporter	kvm-exporter + cobalt refs	Component-specific

Always specify -n <namespace> explicitly in every kubectl command.

Gate: Domain identified and relevant references loaded.

Phase 2: DIAGNOSE / RESPOND

For debugging: follow the triage flow — describe, logs, events, exec. Use read-only commands to gather evidence before proposing changes.

For security: provide concrete YAML manifests and specific configurations. Answer with reference-backed specifics, not generic advice.

For cobaltcore: use component-specific reference knowledge for architecture, metrics, configuration, and deployment details.

Gate: Specific, reference-backed diagnosis or response provided.

Phase 3: VERIFY

For debugging: confirm the fix resolves the symptom. For security: validate against the misconfiguration table in supply-chain.md. For cobaltcore: verify against component test patterns.

Gives 0 of the 12 instructions most containers cloud skills give

Counted across 607 of the 657 authors here whose files we hold, read 2026-08-06

run containers as a non-root userin 69 of 607, across 49 files
use multi-stage buildsin 52 of 607, across 41 files
use Promise.all for independent operationsin 47 of 607, across 13 files
import directly instead of barrel filesin 46 of 607, across 12 files
use ternary instead of AND for conditionalsin 45 of 607, across 12 files
use Set or Map for O(1) lookupsin 42 of 607, across 10 files
create a .dockerignore filein 41 of 607, across 31 files
Read individual rule files for detailsin 39 of 607, across 9 files
authenticate server actions like API routesin 35 of 607, across 7 files
use next/dynamic for heavy componentsin 34 of 607, across 9 files
use React.cache for per-request deduplicationin 34 of 607, across 10 files
copy dependency files before source codein 34 of 607, across 21 files

Said here and by no other author read

read matched references before responding
identify the target Kubernetes domain
specify the namespace in every kubectl command
gather evidence with read-only commands
follow the triage flow for debugging
provide concrete YAML manifests for security

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.